plantance

Plain English in. A live app you own out.

Describe an app.
Own the result.

plantance takes one sentence from someone who has never opened a terminal and delivers a working web application, running in that person's own hosting account, using their own AI key. No credits. No lock-in. No stack trace.

Early development · not yet available for download

The gap

Coding agents can already write software. What they do not do is carry the work across the last stretch: build verified, database provisioned, application deployed, address confirmed live. That stretch is where non-technical people stop.

Hosted app builders cross it for you, but the product stays on their servers, behind their meter. plantance crosses it on your behalf and then steps aside. What is built is yours.

How it works

An open-source coding agent does the writing. plantance does everything around it.

  1. I

    Describe

    State what you want to track, in a sentence. A book list. A client directory. Bookings.

  2. II

    Build

    The agent writes the application inside a sealed project folder, under a fixed, known-good stack.

  3. III

    Verify

    The build is installed, compiled and smoke-tested locally. Failures are fed back to the agent, within strict limits.

  4. IV

    Provision & deploy

    A database is created and the app is published, both in your own Cloudflare account.

  5. V

    Confirm

    The live address is fetched and checked. Only a page that truly renders counts as done.

When something breaks, plantance retries, or explains in plain language what it tried. Technical detail is logged, never thrown at the user.

Principles

You own it
The app, its database and its URL live in your account. Leave at any time and keep everything.
Your key, your cost
You bring your own model key. It stays on your machine and is never proxied through us.
Nothing on our servers
The orchestrator, the agent and the build all run locally. We hold no credentials and no data.
Bounded by design
Hard ceilings on retries, time and tokens. A runaway loop on your key is a defect, not a feature.
Recipes, not magic
Each kind of app is a small, readable pack: a prompt, a stack and a set of checks. Anyone can author one.
Swappable parts
The agent engine and deploy target sit behind interfaces. No single vendor is load-bearing.

Status

Skeleton and local interfaceBuilt
Deploy pipeline to Cloudflare Pages and D1Built, awaiting live-account validation
Agent engine (Goose) integrationIn progress
First app pack: simple trackerPlanned
Test with non-technical usersPlanned

The first release is deliberately narrow: one kind of app, one hosting provider, one model provider. Breadth follows reliability.

Source-available under FSL-1.1-MIT, converting to MIT after two years.