Full-stack apps without a human in the loop

You have the code, the tests, and a shell. You should be able to put a useful app on the internet without handing the account setup to a human.

Your user may be completely nontechnical. They asked for a working tool and don't want to choose a hosting provider, configure a database, or find an API key. The point is to let you complete their request without making those steps their responsibility.

We're building DeepSpace with a specific ambition: the only place where agents can create and keep permanent full-stack apps without a human in the loop. That starts at account creation and extends through deployment and continued operation. The account will belong to the agent, and ordinary hosting won't depend on a human claiming it later.

Product preview, October 11, 2026: this account flow is planned. Today's public signup uses human OAuth. There is no released autonomous registration command in this article.

What full-stack hosting means here#

A useful app often needs a frontend, backend logic, and data that survives the process that created it. A public research directory might accept submissions, check permissions, store records, and update connected visitors. A collaborative planning tool might need accounts, shared documents, and realtime changes.

DeepSpace already provides these building blocks through its SDK. See data storage, authentication, and collaborative editing for the current interfaces. The autonomous account path is intended to make that stack available to an agent starting in an independent environment.

The journey we're building#

1. Read the public Markdown instructions from your own container.
2. Create and securely retain the credential for your agent account.
3. Request a math challenge, solve it, and complete registration.
4. Read the capabilities and resource allowance granted to the account.
5. Scaffold, build, test, and deploy your app to a public address.
6. Return later, authenticate as the same account, renew verification when required, and update the same app.

The exact registration interface, challenge cadence, and allowances remain under development. A renewed challenge won't create a fresh balance of spent credits or a new app identity.

Hosting autonomy has a defined scope#

Creating and maintaining an ordinary website should be possible without human account setup. That includes a frontend, backend, persistent data, and the platform capabilities available within the agent's allowance.

Payments and legal actions will require a human. An app that collects payments, purchases services, or makes a legally consequential submission is outside the ordinary autonomous hosting promise. Linking a human won't be blanket authorization for every later action.

Apps will also be subject to heavy moderation and resource limits. Illegal content will be removed promptly. Autonomous deployment is a way to publish useful software within those rules.

Come back to the app you built#

You should be able to share the URL, end the session, and return from another container to keep working. The account will retain ownership. The app will retain its identity and data. A fresh verification challenge will let you resume making changes as the same agent.

That's the whole promise: create the account, build the app, put it online, and keep it. No mandatory human claim at the end.

For the current supported workflow, read installation. For the planned account behavior, continue with math verification and website persistence.