App Builder
App Builder turns an application brief into a versioned app in LibraOS Cloud. You use it through the Console at console.libraos.com. Create an account on the sign-up page; no invitation or onboarding call is needed.
App Builder and the Console
App Builder is the Console's application workflow. AgentD runs development tasks in your own environment. Cloud Workers add optional hosted execution for AgentD, in beta.
The Console brings together:
- Builds apps. You describe an app, and the Console builds it on the LibraOS Runtime in an isolated project computer. You keep its versions, its checks and its source.
- Sells model access. One credits balance pays for builds, previews, published apps and calls with your own model API keys. A Token Plan covers the same use except builds; see Credits and billing.
- Sets up AgentD and the self-hosted Runtime. The AgentD and Runtime pages show the setup steps for AgentD and for Self-Hosted.
To run LibraOS on your own servers without the Console, start with Getting started.
Build an app
-
Describe it. On Overview, answer "What do you want to build?" in a few sentences, or pick a template. You can also import an existing app from a ZIP or from GitHub.
-
Agree the brief. The brief consultant asks questions and writes a brief for the app. Builds start from that brief.
-
Let it build in stages. Each build runs in an isolated project computer and produces a new version. The stages are:
- Stage 1 · Frontend prototype: the UI, on sample data. When a version passes its checks, choose Lock UI to move on.
- Stage 2 · Data and AI contract: what the app stores and what its AI does.
- Stage 3 · Backend: the LibraOS backend, built against the locked UI and the contract.
- Stage 4 · Acceptance & release.
While a build runs you can watch the project computer, read the logs, or ask for changes in the project conversation.
-
Check each version. A version is checked against the project's pinned acceptance journeys; How it is checked lists them. Screenshots, test reports and other evidence stay with their version.
-
Preview it. Open preview opens the selected version. The preview link expires, and is renewed while you watch.
-
Take the source. Download or push exports a version as runnable source: Download source ZIP, or push it to a GitHub repository. Secrets, sessions and the private project conversation are not included. If you change the code on GitHub, Update from GitHub takes those commits back into the project.
The Console's Deploy page covers running an app on servers you control with the reference stack. Hosting apps in LibraOS Cloud is planned and not available yet.
Console pages
| Page | What it holds |
|---|---|
| Overview | Start a project; the Runtime, AgentD, licence and credits cards. |
| Projects | Your projects, their versions and builds. |
| AgentD | Setup steps for AgentD. The Console does not see your local sessions or tasks. |
| Runtime | How to install the self-hosted Runtime and connect inference. |
| Deploy | Running your apps on your own infrastructure. |
| Licence | Your developer licence record. |
| Credits & billing | Balance, Buy credits, the Token Plan, recent activity and model prices. See Credits and billing. |
| API keys | Model API keys (lk_…) and Runtime keys. See LibraOS model API. |
| Settings | Notifications: low-balance emails. |
Connect your application to a Runtime
An app the Console builds runs on the LibraOS Runtime, and so does an app you write yourself. The runtime APIs are the same wherever the Runtime runs. Set the Runtime's URL and a bearer credential for it:
export LIBRA_OS_URL=https://your-runtime.example
export LIBRA_OS_API_KEY='your-bearer-token'
Runtime keys on the Console's API keys page open a Runtime's own API.
They are separate from model API keys: a model API key calls models at
api.libraos.com and does not open a Runtime.
Follow Create your first agent to create and call an
agent. The Python SDK is asynchronous: use await client.messages.create(...)
inside an async function and an async with Client(...) context.
Setup-generated definitions and templates are editable starters; there is no fixed eight-person team that applications should assume exists.
Add your knowledge
Upload documents, create collections, and bind them to your agents using Workspaces & memory. A website crawler or other connector must be configured and available before it can import content. Creating an account by itself does not connect your website or populate a knowledge base.
Move between deployments
Export the employee and agent definitions and supported bundle contents, import them into the destination, then configure credentials, callbacks, models, and storage for that environment. Verify collection bindings and run your evaluation set. A bundle is not a backup of conversations, jobs, audit history, or every external service.
See portability for environment-dependent features. Current prices are on the Console's Credits & billing page and on libraos.com/pricing; do not build an integration around a fixed price or free allowance.