App Builder and self-hosted Runtime
App Builder in LibraOS Cloud and apps you host yourself use the LibraOS Runtime and the same agent-definition format. The difference is who runs what, and where data is stored and processed.
| App Builder (Console) | Self-hosted Runtime | |
|---|---|---|
| Start | Sign up at console.libraos.com | Install and configure the server |
| What it does | Builds apps from a brief in isolated project computers; sells model API access | Runs the Runtime and your apps |
| Operations | LibraOS runs the Console, builds and previews | Your team runs and updates it |
| Storage | Project versions and evidence in your Console account | Your configured databases and filesystem |
| Model processing | The LibraOS model API and its upstream providers | Hosted providers or local models you configure |
| Offline operation | Not available | Requires local models, embeddings, and compatible tools |
| Running apps in production | Hosting in LibraOS Cloud is planned; export the source and run it yourself | Your infrastructure |
The two combine. A self-hosted Runtime can use the LibraOS model API with an
lk_ key, and an app built in the Console can be downloaded or pushed to
GitHub and run on your own servers.
Self-hosting does not automatically prevent outbound model, embedding, search, or callback traffic. See Security.
Same interfaces, environment-dependent capabilities
An application can use the same API shapes against any Runtime, but must supply the correct base URL, credential, and installed agent ID. The available models, tool services, persistence, permissions, and release versions can differ. Check Portability before moving an integration.
Moving between deployments
- Export the employee/agent definitions and the supported knowledge bundle.
- Provision the destination runtime and its stores.
- Import definitions and knowledge; verify collection bindings.
- Configure destination credentials, model IDs, tool callbacks, and ownership.
- Run your integration and evaluation checks before redirecting traffic.
An employee bundle does not promise to move all conversation history, observational memory, job state, audit records, or external credentials. Plan those separately if your migration needs them.
For current prices, see the Console's Credits & billing page, Credits and billing and pricing.