FlareStudio FCC Workbench

Tactical infrastructure for building, testing, and deploying Sovereign AI Agents on the Flare Network.

What is this?

The FlareStudio FCC Workbench is a CLI toolkit designed to simplify development for Flare Confidential Compute (FCC). It turns the TEE, proxy, and contract setup into a guided developer flow.

Quick Start

Install the workbench globally:

npm install -g @flarestudio/fcc-workbench

Commands

Main flow: guided onboarding

Use this first. It is the recommended end-to-end path for setting up a Coston2 FCC project:

flarestudio-fcc-cli onboard --profile coston2

If the flow stops partway through, continue with:

flarestudio-fcc-cli resume

The guided onboarding flow handles:

• project scaffolding
• environment setup
• local stack startup
• InstructionSender deployment
• extension registration
• TEE version allowlisting
• tunnel creation
• TEE machine registration
• E2E validation

Recovery and manual commands

Use these when you need to inspect or recover a partially completed onboarding run:

flarestudio-fcc-cli doctor
flarestudio-fcc-cli start
flarestudio-fcc-cli stop
flarestudio-fcc-cli tunnel
flarestudio-fcc-cli allow-tee
flarestudio-fcc-cli register-tee
flarestudio-fcc-cli test-e2e

• doctor checks your local prerequisites and configuration before you start onboarding.
• stop shuts down the local FCC Docker stack for the current project so you can reset ports, restart cleanly, or recover from a failed run.

Utility commands

Use these for standalone tasks:

flarestudio-fcc-cli init
flarestudio-fcc-cli encrypt
flarestudio-fcc-cli send

Current status

The onboarding docs intentionally mark the Coston2 FTDC/action-result step as coming soon until the hosted environment is confirmed stable. Everything before that point is documented as the supported local flow.

The hidden .flare-fcc/ folder is created automatically inside each project to store onboarding state and resume data. It is not the CLI command name.

Project Structure

When you run init, the workbench generates:

• extension/ — Your agent logic
• contracts/ — InstructionSender Solidity contracts
• scripts/ — Deployment and management scripts
• docker-compose.yml — The FCC stack
• .flare-fcc/ — Hidden local state used by resume and onboarding recovery

Security

This workbench allows for local testing of TEE logic. While the cryptography is production-grade (ECIES/secp256k1), real hardware isolation requires deployment to registered Flare TEE machines.

Built with 🥃 by FlareStudio