Solana builders can now create and deploy on-chain projects directly from their browser. No downloads. No wallet connection. No wasted time. Start building with Brik today. Contract: BrikD3tfzSL7deBUQsxzKjWdYkAHKpFKmt89KySxpump

We are building this tool for new devs who don't understand complexity. We don't want to scare them away. Our docs have all that detail. Big update coming soon!

If you try Brik today, reply with the first thing that feels slow, confusing or broken. The current product is public and anonymous. Real builder friction is more useful than another private demo. brik.builders

Solana builders: reply with the Anchor error that cost you the most time. Compiler error, IDL mismatch, account constraint, stale program ID, anything. Those are the cases Brik should learn to make boring.

Mainnet is the one deploy button Brik will not rush. Localnet works today. Devnet sharing comes first. Mainnet waits until funding, custody and approval boundaries are explicit, because no build tool should hide who signs or pays.

Brik's docs list the current toolchain, workspace lifecycle, limits, supported packages and everything that is not live yet. If the product and the docs disagree, that is a bug. brik.builders/docs

Brik's rate-limit store never receives a raw IP address. The request address is salted and hashed before it becomes a Redis key. Limits survive server restarts without turning visitor addresses into app data.

Anonymous access has real limits today: five workspace starts and 30 agent requests per visitor, per hour. The counters apply across the deployment, not inside one server process, and reset on the hour.

Every metered Brik agent turn ends with its actual input and output token counts plus an estimated dollar cost. Usage comes from the model response. Builders should be able to see what the agent spent.

After an agent turn, Brik reads the project back from the workspace before updating the editor. That catches files changed by shell commands too. The screen reflects what is on disk, not only what the model says it edited.

The Brik agent cannot write outside the project. Every file path must be relative. Absolute paths and any path containing .. are rejected before the workspace is touched. The sandbox boundary also applies inside the sandbox.

After Brik deploys a program, the suite runs with --skip-build and --skip-deploy. That is deliberate. The tests hit the exact program and state produced by the visible deploy instead of quietly replacing either one.

Cargo fingerprints include absolute paths. Copying the project to a new directory turns a warm build cold. Brik overlays each template at /workspace/project, where the image was prebuilt, so Cargo can reuse the target cache.

Every Brik image build generates a fresh program keypair. Before the template builds, Brik runs anchor keys sync and reads the source back from disk. That keeps declare_id!, the deployed address and the tests pointed at the same program.

One correction from an earlier post: the live E2B workspace does not finish in 12 to 14 seconds. The current full run is about 40 seconds from Start building to deployed on the workspace validator with tests green. Measured beats guessed.

Brik runs each cloud workspace in its own Firecracker microVM. That is why Agave 3.1.9 can boot its validator unmodified with io_uring available. No shared Docker host and no relaxed seccomp profile.

Small detail for people who build with the keyboard: ⌘B toggles files ⌘J toggles the terminal ⌘Enter redeploys ⌘/ focuses the agent Windows uses Ctrl. What shortcut should Brik add next?

When Brik's included agent budget runs out, the work does not have to stop. Add your own Anthropic key and keep building. It stays in that browser tab, goes only with your requests, and is never stored on the server.

The launch brought a lot of new eyes to Brik. Good. Now the product has to earn that attention. Anyone can open brik.builders and run a real Anchor project today. Back to work.

Every Brik template has to pass twice against the same workspace before it ships. That catches state collisions a fresh validator can hide. Redeploy is part of the test, not a button we hope works. What Solana app should become template number five?

Brik workspaces run with network egress off, so builds only use dependencies already baked into the image. Today that includes anchor-lang, anchor-spl, @coral-xyz/anchor and @solana/spl-token. Which Solana crate or package should we add next?