CARLOS
A set of conventions for architecting and deploying web apps
An opinionated framework for building, deploying and running robust web apps.
A set of conventions for architecting and deploying web apps
A web framework using Go + SQLite + a design system for building CARLOS apps
An open-source deployment platform for deploying CARLOS anywhere, with carloku.com ready to sign up for today
A set of defaults for the agentic age that bring a host of benefits:
Cost-effective, Available, Replicated, Lightweight, Open, and Secure
Before CARLOS
Single big deployment, single big database
With CARLOS
Lots of small instances, can be deployed independently
By default, CARLOS apps are broken down into full-stack deployable instances that run as single processes with embedded databases that can run independently or as part of a SaaS like app deployment. This introduces huge flexibility and portability gains without compromising user experiences.
| Before CARLOS | With CARLOS | Benefits |
|---|---|---|
| Monolithic multi-tenant apps | Single-process per tenant | Much more flexibility |
| Centralised multi-tenant databases | Database per-tenant | More secure, more control |
| Nightly backups | Continuous streaming | Robust data-storage |
| Single-deployment per app | Flexible deployment per tenant | Easily deploy multi-platform, multi-region, or self-hosted |
| Everyone updates at once | Tenants can choose whether to upgrade | Customers have more control |
Before CARLOS
Platform / Database / APIs / Proxies
CARLOS platform, self-contained, addons optional
The initial question is: what if we could have all these benefits, without any compromise? How do we use agents to amplify a vision for a better web?
| Before CARLOS | With CARLOS | Benefits |
|---|---|---|
| Existing pre-agentic frameworks | Agentic-aware from day one | Maximal token efficiency |
| Slow, interpreted languages | Fast, compiled languages | Huge day-one performance |
| API as an addon | API as first class | Build apps that agents can use |
Before CARLOS
With CARLOS
Single process,
embedded database
Unlocking the promise of 100x productivity requires a mindset shift: what if everyone on a team can build features, as close to production as possible?
| Before CARLOS | With CARLOS | Benefits |
|---|---|---|
| Complicated development environments | Simple dev env with few dependencies | Little to no dev/prod disparity |
| Prototype -> Plan -> Implement | Prototype and implement in the same step | Programmers and non-programmers alike move quicker |
| Slow, clunky dev tools and CI | Fast compile, fast runtime, fast CI | Robust well-tested code with more reliable tests |
| Slow, brittle preview environments | Instant full-stack preview environments | Test multiple versions of features side-by-side |
| Clunky wrapped web apps for native | Properly rapidly-built native UI apps | Shared modules and database schema |
By simplifying the architecture, but without compromising on robustness or security, CARLOS apps gain a host of operational benefits.
| Before CARLOS | With CARLOS | Benefits |
|---|---|---|
| A stack of expensive tools | Much more development and runtime efficiency | Much higher cost:performance ratio |
| Prototype -> Plan -> Implement | Prototype and implement in the same step | Programmers and non-programmers alike move quicker |
| Slow, clunky dev tools and CI | Fast compile, fast runtime, fast CI | Robust well-tested code with more reliable tests |
| Complex container orchestration | Lean process orchestration | Lightweight operations that are far more efficient |
Before CARLOS
Mixing customer data
With CARLOS
Isolating customer data
Starting from tenant isolation, and going all the way to full end-to-end-encryption if you need.
| Before CARLOS | With CARLOS | Benefits |
|---|---|---|
| Mixing customer data | Isolating customer data | Much narrower blast radius |
| Scoped database queries | No risk of query leakage | Greater portability e.g. true SQL access to data |
| Plaintext almost everywhere | Encryption encouraged | Security at rest, on disk and in transit |
| Opaque security posture and compliance | Declarative trust classes | More transparency about application security |
| Third-party security scanning | Continuous security scanning baked in | Encouraging good security hygiene out of the box |
Before CARLOS
Accessibility optional
With CARLOS
More inclusive applications by default
| Before CARLOS | With CARLOS | Benefits |
|---|---|---|
| Accessibility optional | WCAG 2.2 AA audit-ready encouraged from the start | More inclusive applications by default |
| Closed source | Encouraging open source and open protocols | More adaptable software |
| I18n maybe | Comprehensive I18n and L10n | Reach global audiences sooner |
| One size fits all | More customisability per customer | Many more viable options for custom experiences |