Describe what you want the way you'd explain it to a friend. Australis asks a few plain-English questions, sketches a plan, and only builds once it looks right to you. Nothing is built behind your back.
Attach a logo or a reference. Pick where it saves. That's the whole setup.
Every build starts with a size: one polished page in about a minute, an MVP of the 3–4 core screens, or the full app built in phases you approve. Good answers are pre-picked at every step — Next, Next, Next, build.
The plan is the contract: sketches of every screen, untick what you don't need.
One toggle at the top of the window. No exports, no handoffs, no "let me convert that for you" — Canvas and Code are the same folder on your disk.
In Canvas, Ozzy plans and builds with you. In Code, the agent proposes changes as reviewable diffs — accept or reject, file by file.
Claude writes the code on every build — one model, so results don’t drift between machines.
Every build ends with receipts, not promises. Australis proves the app builds, boots, and that every page actually loads — and the labels never exceed the evidence. If something didn't pass, it says so.
Examples of apps you could describe in a sentence — each with its own look, none of them from a template.
The line between free and paid is simple: we charge when we spend money on your behalf — hosting your data, running AI, shipping your code. Full pricing details →
And the honest part: if a build fails verification, you get half its credits back.
Yes — every project is a plain folder on your computer, in a stack you chose. Open it in Code view, in another editor, or hand it to a developer. Export everything and walk away any time; there's no lock-in.
That's who Canvas is for. You describe what you need in your own words, answer a few plain-English questions, and approve a plan before anything is built. You never have to see code — but it's there when someone on your team wants it.
No. Builds run on Australis's own models, so there is no key to obtain, paste or pay for separately — Claude writes the code and your build credits cover it. You do need a beta invite and to be signed in, because builds run through the Australis control plane.
Your project folder lives on your machine — ~/Australis by default, or a folder you choose. Building sends your request, and the parts of the project needed to answer it, to our servers in Sydney and on to the model. Publishing uploads the app, and an Australis Cloud database lives on our managed backend.
After every build, Australis proves the app compiles, boots, and that each page responds — and shows you the receipt. Labels never exceed evidence: if a check didn't pass, the banner says so instead of claiming success.
macOS 13 or newer (Apple silicon and Intel), or Windows 10 (build 1809) or newer, 64-bit. Around 400 MB of disk, and an internet connection when you build with a cloud model.