Skip to content

Generation is
the first minute.

The hard part is running the app, connecting it to what the business already uses, and shipping it somewhere real. Klego is built around everything that follows the prompt.

After the prompt00:01 → live
  1. 01GenerateThe first versionfirst minute
  2. 02RunA live container and URLbuilt in
  3. 03ConnectYour accounts, through OAuthbuilt in
  4. 04PublishYour code, repo and domainbuilt in
InstructionWorking software

A page is not
an app.

Prompt-to-app tools often stop when the interface looks right. That is exactly where Klego’s workbench starts.

Where generation stops

A convincing first screen.

Useful, but still disconnected from the systems, runtime and ownership model that make it production software.

Where Klego starts

A running, connected system.

A live container, saved workflows, editable files, undoable history and a publish action that ends on your domain.

ContainerOAuthSourceGitDomain

Four principles that decide arguments.

When a shortcut conflicts with one of these, the principle wins.

  1. 01

    Show the running thing

    A generated page proves little. The engineering goes into booting it and getting it in front of you as software.

  2. 02

    The connection is the product

    Writing a form is easy. Writing one that puts a record into your Salesforce org is the part that took the work.

  3. 03

    Name the escape hatches

    Code, diffs, ZIP, your own repo, your own domain. ‘Can I leave?’ should be answered before you sign up.

  4. 04

    Claim nothing unverified

    Where this site has a slot for proof we do not have, it says so—marked, not filled with a comfortable number.

The people belong here.Placeholder — team details pending

This space is deliberately reserved. No head count, founding date, funding or location is stated until the real details can replace the placeholders.

PortraitReserved, not invented
RoleReserved, not invented
Short lineReserved, not invented
Real detailReserved, not invented