Docs

How Brik runs.

What happens between Start building and a deployed program, what the workspace carries, and what is not live yet.

Updated 2026-09-01

What Brik is

Brik is a browser workspace for Solana programs. Pressing Start building starts a container from the Brik toolchain image, boots a validator inside it, writes the project in, builds it with Anchor, deploys it to that validator, and runs the test suite. Every line of output streams into the terminal as the container produces it.

Everything on the workspace screen is read out of that container: the program id, the deploy signature, the wallet and its balance, the files, the test results. Nothing is staged or simulated.

No account, no local toolchain, no Docker on your machine.

A run, step by step

  1. 01Start the container.A sandbox from the Brik toolchain image, with no network egress.
  2. 02Boot the validator.A validator inside the sandbox, and a wallet funded with 1,000 test SOL.
  3. 03Write the project in and build it.The template replaces the scratch program, then anchor build runs against the image's warm target directory.
  4. 04Deploy to the workspace validator.1.266 SOL of rent, paid from the funded wallet.
  5. 05Run the suite.anchor test against the deployed program. The result on screen is the suite's own output.

On the live site a run takes about 40 seconds from Start building to a deployed program with its suite green. Redeploy runs the build, the deploy, and the suite again in the same workspace.

Templates

Four Anchor programs, each verified by running it twice against the same workspace, which is what Redeploy does. A suite that only passes on a fresh validator does not ship.

TemplateWhat it doesStackVerified
Tip jarAccept SOL tips, with the running total and the tip count on chain.ANCHOR · SYSTEM PROGRAM11.7s · 4 tests
NFT mintMint from a capped collection, with Metaplex metadata and a master edition.ANCHOR · METAPLEX12.0s · 2 tests
Token gateProve an SPL balance on chain and issue a pass a server can read back.ANCHOR · SPL TOKEN14.2s · 3 tests
USDC checkoutTake USDC payments where the order account is the receipt.ANCHOR · SPL TOKEN13.8s · 3 tests

Describing an idea on the start page opens the default project, Tip jar, with your description as the run's objective. Ask the agent to build it from there.

The agent

The agent panel is a task runner, not a chat. Give it an objective and it reads the project first, edits the files the change touches, runs the build and the tests, and lists each command with its result. It reports nothing a command did not report, and a failing suite sends it back to the file it just edited.

It edits and runs commands without asking first. The sandbox has no network egress and a fixed lease, and nothing outside it is reachable from inside.

Agent time is metered per visitor. When the hourly budget is spent, the composer offers to continue on your own Anthropic key. The key is sent with your requests and kept in the tab only; it is never stored on the server.

Toolchain

ToolVersion
Anchor0.31.1
Rust1.85
Agave3.1.9
Node22

Egress is off inside the workspace. It cannot fetch a crate or an npm package, so a project can only use what the image already carries. Reaching for anything else fails the build inside the workspace.

  • Crates: anchor-lang, with init-if-needed; anchor-spl, with metadata
  • Packages, for the suite: @coral-xyz/anchor, @solana/spl-token, chai, mocha

Shortcuts

is Ctrl off a Mac.

KeysAction
BShow or hide the file rail
JShow or hide the terminal
Deploy, or redeploy, the program
/Focus the agent composer
On the start page: start building from the description

Limits, and what is not live yet

A workspace lives for 15 minutes and is released when you close the tab. Nothing is saved: there is no account yet, so a closed tab is gone. Every run deploys to localnet, the validator inside the sandbox.

Per visitor, per hour:

  • 5 workspace starts
  • 30 agent messages, inside a metered token budget

Not live yet:

  • Devnet deploys and shareable preview URLs
  • Saving a workspace: signup and persistence
  • GitHub import and push
  • Billing
  • Anything on mainnet

Something on this page wrong? info@brik.builders