FROM IDEA TO A LIVE SOLANA APP. IN ONE TAB.
Describe it or pick a template. Lathe boots a validator of your own in 1.9S, funds it with 1000 SOL, then builds, tests, and deploys while you watch. No Rust, Anchor, or Solana setup, and NO SIGNUP.
WHERE THE RUN GOES.
Every workspace runs the same machine: a container boots a validator, the toolchain builds, the suite tests, the program deploys, and the agent reads all of it before it claims anything. Click any part.
- DESCRIBE
- BOOT
- WRITE
- BUILD
- TEST
- DEPLOY
ANCHOR BUILD, FOR REAL
The compiler runs in the container and its output streams into the terminal as it is produced. A warm cache makes the second build almost free.
- FIRST BUILD
- ~3S
- WARM BUILD
- ~0.3S
- OUTPUT
- THE COMPILER'S OWN
01#[program]02pub mod project {03 pub fn send_tip(04 ctx: Context<SendTip>,05 amount: u64,06 ) -> Result<()> {07 let jar = &mut ctx.accounts.jar;08 jar.total = jar.total.checked_add(amount)09 .ok_or(TipJarError::Overflow)?;10 Ok(())11 }12}
TEST SOL PER WORKSPACE
FUNDED BY ITS OWN VALIDATOR IN 1.9 SECONDS. NO FAUCET, NO WALLET TO CONNECT.
TIP JAR TESTS PASSING
MEASURED BY PNPM VERIFY-TEMPLATES, TWICE IN ONE WORKSPACE.
PICK A TEMPLATE.
VERIFIED · PNPM VERIFY-TEMPLATESFour real Anchor programs with real test suites. Each one is built, deployed, and tested twice in a real workspace before it is listed here.
- TIP JARAccept SOL tips, with the running total and the tip count on chain.
- NFT MINTMint from a capped collection, with Metaplex metadata and a master edition.
- TOKEN GATEProve an SPL balance on chain and issue a pass a server can read back.
- USDC CHECKOUTTake USDC payments where the order account is the receipt.
TWO WAYS IN.
Builders start from a sentence. The skeptical read the terminal first. Both get the same machine, and neither signs up.
START FROM A SENTENCE
- 01DESCRIBE THE APP OR PICK A TEMPLATE
- 02THE VALIDATOR BOOTS AND FUNDS 1000 SOL
- 03THE TEMPLATE BUILDS, DEPLOYS, AND TESTS
- 04ASK THE AGENT FOR A CHANGE
- 05REDEPLOY AND READ THE OUTPUT
WHAT THE MACHINE RAN
$ anchor build Finished release [optimized] in 3s $ anchor deploy Deploy success · 4.3s · 1.266 SOL rent $ anchor test --skip-build --skip-deploy 4 passing
EVERY LINE ABOVE WAS READ OUT OF A CONTAINER DURING A MEASURED RUN, NOT TYPED FOR THIS PAGE.
OPEN A WORKSPACEASKED
A LOT.
WHAT IS LATHE?
A browser-native workspace for Solana: a container with Rust, Anchor, the Solana CLI, and a validator of its own, plus a coding agent, in one tab. It is made in Colorado.
DO I NEED TO INSTALL ANYTHING?
No. The toolchain is baked into the workspace image: Anchor 0.31.1, Rust 1.85, Agave 3.1.9, Node 22. You need a browser.
WHERE DOES MY PROGRAM DEPLOY?
To the validator that booted for your workspace, in a few seconds, with 1000 test SOL to spend. Devnet deploys, shareable preview URLs, and forking are not built yet, and the workspace says so instead of pretending.
IS THERE REALLY AN AGENT?
Yes. It lists, reads, writes, and runs commands inside your container and shows each step as it happens. Its model spend is metered per visitor per hour; when that runs out you can use your own API key, which stays in your tab.
DOES MY WORK PERSIST?
Not yet. A workspace lives for its lease and nothing is kept when the tab closes. Signup and saved projects are the next slice, and signup will gate saving, never the first run.
WHAT DOES IT COST?
Nothing today. Each visitor gets a handful of workspace starts and a metered agent budget per hour, so nobody can drain the machine for everyone else.
WHY THE PIXELS?
Every number on this site was read off a machine, and a readout is honest about being one. The type is Departure Mono, the mark is a turned ball shaded the way a one-bit screen would draw it, and the orange is where the light lands.