Fast, cost-efficient, good: pick all three with rastrillo.

Fifteen lines in. An admin you can read, out.

Generated, not interpreted — everything it writes, you can read.

name  = "ticket_types"route = "/admin/ticket_types"store = "exclusive"[list]columns = [{ field = "Name" }, { field = "Price", kind = "money" }, { field = "Status" }]search  = true[[list.filters]]field  = "Status"values = ["draft", "on_sale", "sold_out"][form]basics   = [{ name = "Name", required = true }, { name = "Price", kind = "money", required = true }, { name = "Status" }]advanced = [{ name = "MaxPerOrder" }]

Boring machinery, deliberately

Go's standard library, SQLite, and files you can read — nothing decided behind your back.

Filesystem routing

actions/orders/[id]/cancel.POST.go becomes POST /orders/{id}/cancel — the directory structure is the route table. Bracket segments are path params, the filename suffix is the HTTP verb, and rastrillo generate writes it all into a plain gen/router.go on Go's standard http.ServeMux: committed, readable, diffable.

Platform-ready by default

rastrillo.Run speaks the CARLOS platform's activation contract end to end — hibernating instances, carlos-app@ systemd unit tenants, plain instances, and a bare dev fallback, no separate integration per deployment shape. Hibernation is the cost-efficiency receipt: your app isn't running when nobody's knocking, and the platform wakes it when someone does.

Localization built in

Declare your locales and /fr/orders and /orders reach the same route. Request-scoped T/Tf fall back through catalogs so a missing translation stays visible, never blank — and generate --check fails loudly on incomplete catalogs before you ship, not after.

A UI vocabulary, zero JavaScript

rastrillo/ui ships list-screen and form partials plus design tokens: light and dark, WCAG AA contrast, and not one line of client-side JavaScript. examples/blog is a real blog, admin side and all, from stock components only.

One binary, no toolchain sprawl

go install gets you the CLI, go build gets you the app — a single static binary with SQLite compiled in. No bundler, no separate codegen service, no runtime to babysit. The framework whose family motto is "no build step" doesn't ship one to your visitors either.

Run it locally

One command to install, three more to a running app.

go install github.com/carlosframework/rastrillo/cmd/rastrillo@latest

Or via Homebrew: brew install carlosframework/tap/rastrillo.

rastrillo new myapp

Writes a go.mod, one starter action, a main.go wiring rastrillo.Run, and the rastrillo/ui design tokens — then runs generate once, so the next step just works.

cd myapp && go get github.com/carlosframework/rastrillo@latest && rastrillo dev

Visit localhost:8080 — that's your app. Edit an action, save, refresh: rastrillo dev regenerates, rebuilds, and restarts for you in about a second. A save that doesn't compile keeps the previous build serving while you fix it.

Deploy it for real

CARLOS is self-hostable — one binary, a bucket, and DNS. No PaaS account to sign up for.

brew install carlosframework/tap/carlos

Or grab a binary directly from carlosframework/releases.

GOOS=linux GOARCH=arm64 go build -o myapp-binary ./cmd/myapp

carlos ship -app myapp -version $(git rev-parse --short HEAD) myapp-binary
carlos promote -app myapp <version> stable
carlos add -app myapp -kind instance myapp.yourdomain.com

The same sequence — against a real S3-backed bucket, a real edge, a real certificate — that put rastrillo's own example live at helloworld.dev.oncarlos.com. Standing up the box, bucket, and DNS is the one-off part; from then on every deploy is ship then promote.

What's real today

A young framework that ships its status on its homepage — this list moves when the work lands, not before.