AI apps for
your clients.
Start from reusable application code and Runtime capabilities. Spend the project on your client’s workflow, integrations and acceptance criteria.
Build in your own stack or request Cloud private-beta access.

Reuse the groundwork.
Keep the common application patterns. Make the client-specific work explicit.
Start with LibraOS
- Application source and runnable starter guides
- Runtime agents, knowledge, memory and tools
- SDK and APIs for your development stack
- Documented model and deployment choices
Shape the client project
- Users, interface and business workflow
- Data sources, integrations and identity
- Acceptance checks and human review points
- Source handover, operating costs and support
Agree the handover.
Make these deliverables part of the project scope. They are acceptance criteria to verify, not a promise that a generated build has already passed.
Define
Document the workflow, sample data, integrations and acceptance criteria before building.
Build
Adapt the source and review the interface. Keep client-specific changes in version control.
Verify
Test the agreed flows with the configured Runtime and models. Record failures and unresolved work.
Deliver
Agree source access, release instructions, licensing and who will operate the application.
Inspect the work.
Use real source as the starting point for your technical evaluation.

Run a complete starter
The Personal Assistant includes a React + TypeScript frontend and documented Runtime setup. Follow the guide to configure models, build the frontend and verify the application.
Run the Personal AssistantInspect a support recipe
The Customer Support recipe demonstrates knowledge retrieval and a tool callback with sample data. It is a Runtime integration example, not an end-to-end Cloud delivery demo.
Read the support recipe ↗Scope the first project.
Bring a client brief and the workflow you want to deliver. Discuss a technical walkthrough and the checks that would make it useful.
Assisted pilot
From US$3,000
One-time engagement. A written SOW defines scope and schedule. Production licensing, model usage and ongoing infrastructure are separate.
Talk to LibraOS salesInclude the workflow, client data restrictions, integrations, intended deployment and target date.
Review the cost structureChoose how to build.
Cloud provides an AI-assisted project workspace. Developer Platform lets your team continue in its own stack.
Cloud is in private beta. A new account does not automatically enable project access, builds or exports.
Build locally with Developer Platform