JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 27
  • Score
    100M100P100Q81464F
  • License ISC

Tactical Workbench for Flare Confidential Compute (FCC). Scaffold, encrypt, and relay sovereign AI agents.

Package Exports

  • @flarestudio/fcc-workbench
  • @flarestudio/fcc-workbench/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@flarestudio/fcc-workbench) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

FlareStudio FCC Workbench

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

npm version License: ISC

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:

flare-fcc onboard --profile coston2

If the flow stops partway through, continue with:

flare-fcc 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:

flare-fcc doctor
flare-fcc start
flare-fcc stop
flare-fcc tunnel
flare-fcc allow-tee
flare-fcc register-tee
flare-fcc 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:

flare-fcc init
flare-fcc encrypt
flare-fcc 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.

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

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