Better
10Ă—lower running costsfrom reducing AWS resources
87%less JavaScriptby rendering pages on the server
- Agent access
- Local development
An AI-driven software development approach for building and shipping uncompromising apps in the agentic age
Pass this to your agent and take it from there.
A full-stack go web framework. Everything you need to build CARLOS apps today.
Deploy your CARLOS apps live quickly and easily to a global app platform.
Your agents can build any app.
Using CARLOS principles and tools,
they come out better.
The CARLOS architecture is a smorgasbord of decisions for building modern apps that are performant, robust, secure, and accessible, and cost 70%–80% less to run than traditional web apps.
Rastrillo lets you build apps like this today, with an extensive, and growing list of features for building all kinds of apps.
CARLOS Platform lets you deploy apps and static sites quickly and easily, either via a hosted service, or self-hosted on your own hardware.
CARLOS, Rastrillo, and the platform follow The Eleven Factors: principles to follow when building apps with AI.
What makes CARLOS different?
By combining GenAI, old school computer science principles, and embracing modern tech, CARLOS rejects both monoliths and microservices, in favour of many small full-stack instances.
Faster
12Ă—faster to shipby building with agents on CARLOS principles
4.5Ă— faster first render
5Ă— faster responses
Harder
Customer isolationSeparate every customer’s data
- Enterprise sign-in
- Defence against common security threats
- Auditing at every step
- Build E2EE where required
Stronger
1–2sbackup latencyrather than nightly
- Regional hosting
- Portable data
- Deploy in seconds with zero downtime
How it works
Monolithic multi-tenant app
Before CARLOS
- Cloud provider
- Centralised RDMS
- Memory Cache
- Cluster orchestrator
- Containers
- Background worker
- App server
- Web server
- Load balancer
- Observability layer
With CARLOS
- Cloud provider, on-prem, or hybrid
- CARLOS Platform
- Single-process apps each with their own embedded database
SPA on static hosting
Before CARLOS
- Closed Platform as a Service
- Client side JS Framework app
- Third-party auth provider
- Third-party database provider
- Third-party content provider
With CARLOS
- Cloud provider, on-prem, or hybrid
- CARLOS Platform
- Single-process apps each with their own embedded database
A single-process CARLOS app provides its own self-contained web app, HTML, CSS, and JS. Each tenant can serve their own API, expose their own MCP, and provide a complete CLI: all in the same binary.
What about scaling? Across all tenants, you get planet-scale. Per-tenant, typical database writes per second on commodity CPUs are in the hundreds per second, and reads are in the thousands if not tens of thousands. Good problems to have when you get there.
Numbers based on real data from Tito. The agents insisted on measuring everything. See how
How we measured
Measured on 24 October 2026 from one machine, using normal URLs and persistent HTTP connections. The load test increased in twelve-second stages to 320 requests per second. At that rate, the cached Tito page returned 3,839 responses with no errors and a 19.7 ms 95th-percentile response time.
First Contentful Paint measures when content first appears. We averaged five alternating desktop Chromium visits to each AwesomeConf page: Classic and CARLOS. Each visit used a fresh browser context with browser caching disabled and no network throttling. Server-side page caching stayed enabled.
5Ă— faster responses: 13.6 ms versus 73.5 ms at the same 40 requests/second.
95% of cached HTML responses completed within 20 ms, with zero errors. First content appeared in 168 ms on CARLOS versus 758 ms on Classic, averaged over five visits each.
JavaScript bytes transferred averaged 667kB per visit on ti.to and 85kB on go.tito.io, from five visits to each page in headless Chromium with a fresh browser context and cache disabled each time.
Existing Tito · Tito on CARLOS this section was generated by 🤖
What does better mean?
Do all the hard things that AI makes easy
Speed
If you care about moving fast and making performant apps, speed underpins the CARLOS architecture.
- Faster builds by reducing dependencies
- Quickly iterate new features, skip prototyping
- The joy of "copy and restart" backed by robust infrastructure
- Performance thresholds you'll never reach: for every tenant
An agentic embrace
CARLOS is built by agents following the 11 factors.
- Agent-driveable, human-operable
- CARLOS apps can be used by humans and agents alike
- Web apps and CLIs in the same binary
- Each tenant gets their own API endpoints
Ready for native
The most common database for native apps? SQLite. CARLOS apps make it delightfully easy to build native apps on top.
- Share database schema with native apps
- Data is already isolated per tenant
- Share application logic between web and native apps, with fully native UIs
Accessibility
Turn back the tide of non-inclusive software.
- Demand WCAG 2.2 AA compliance from day one
- Ship apps that are accessibility audit-ready and stay that way
- Acknowledge the irony that human-accessible is also agent-accessible
Save costs and cut carbon by maximising efficiency while gaining capabilities
Value for money
Ever feel like compute got cheaper but software got more expensive?
- Eliminate waste from technology spend
- Cut TCO by 70% or more without compromising
Carbon conscious
CARLOS is all about doing more with less.
- Use 30x less compute for equivalent or increased capabilities
Data resilience and control
Each tenant database is continuously streamed to object storage.
- Easily provide full access to customer data
- Back up with 1–2s latency rather than nightly
- Backup becomes part of operations
Robust deployments
CARLOS apps feel like SaaS apps, but split compute and data by tenant, unlocking a host of benefits.
- Get features live within seconds
- Deploy in seconds with zero downtime
- Get the flexibility of single-tenant with the UX of multi-tenant
Stay in control
Sovereignty and vendor freedom
CARLOS apps compile to single binaries, which can be placed anywhere in the world, on any hardware.
- Cloud, on-prem, hybrid: all first-class
- Deploy apps or instances of apps to any region
- Use one provider or many
Security
Ace your next ISO27001 or SOC2 audit.
- Separate every customer’s data
- Build E2EE where required
- Trivially deploy any app on-prem where required
Customisability
When every tenant has their own instance, the opportunities for customisation are infinite.
- Build custom apps for customers on a shared core
- Let customers run their own version
Flexibility
Alongside control, CARLOS gives you the ability to mix and match deployments.
- Big customer? Give them dedicated compute
- Not everyone has to upgrade at once
- Release pipelines let you roll features out gradually
Who is using CARLOS?
CARLOS is built by the people behind Tito and Jelly, serving real customers, and extracted from the lessons learned in the process.
12Ă— faster to ship
Using the CARLOS principles, Team Tito build their latest release that combined their 10 year old Rails app and their most recent Pro app. CARLOS allows building new features at a velocity not seen before, and allowing customers to locate their data in any one of 7 regions.
Read the Tito storyNew opportunities from on-prem installs
Jelly's ground-up rewrite using Rastrillo meant that it inherited performance budgets and clean separation of customer data, along with the ability to deploy on-prem, unlocking sales opportunities that were impossible before.
Find out how Jelly did itThe E2EE Messenger
“I want to make a chat app. It should be end to end encrypted. Should it use SQLite?” Find out about the app that led to the creation of CARLOS.
Learn about ElevenReady to get started?
Pass this to your agent and take it from there.
A full-stack go web framework. Everything you need to build CARLOS apps today.
Deploy your CARLOS apps live quickly and easily to a global app platform.