Self-hosted CMS

Mini CMS

For development studios

A minimal CMS for projects, teams, and a clean public API.

Manage portfolio work, team members, and structured content collections from one quiet dashboard — built with TanStack Start, Turso, Drizzle, Better Auth, and Resend.

Quick start

git clone https://github.com/lakubuDavid/mini-cms
cd mini-cms && bun install
Illustration of a coworking figure considering a structured board
License
Apache-2.0
Open source
Yes
Field types
4
API cache
60s

The dashboard

Every view, in one quiet place.

Select a view to see what it looks like — the description always matches the screenshot.

Mini CMS — Dashboard overview

Capabilities

Everything a small studio needs — nothing it doesn't.

Collections

Generic tables for projects, team members, testimonials, and future content models.

Public API

Expose collection data through workspace-scoped endpoints with pagination, caching, and rate limiting.

Invite flow

Send invite links to collaborators and keep dashboard access centralized.

How it works

From database to API in three steps.

  1. 1

    Connect your database

    Add TURSO_DB_URL and TURSO_AUTH_TOKEN to .env, then apply the schema to your Turso database.

  2. 2

    Model your content

    Create collections and text, url, number, or boolean fields from the dashboard — no code required.

  3. 3

    Read it anywhere

    Fetch GET /api/collections/:slug from any frontend, or sync types locally with the CLI.

Illustration of a pilot guiding a self-hosted vessel

Self-hosted by default

Your data, your infrastructure, your bill.

Mini CMS runs on your Turso database and your Vercel (or any Node) deployment. No SaaS subscription, no vendor lock-in — just a tiny open-source app you own.

  • Apache-2.0 license — free for commercial use
  • One SQLite-compatible database (Turso) — pennies at scale
  • Edge-ready, serverless-first — deploy to Vercel, Cloudflare, Fly, or a VPS

Developer experience

A CLI for schema sync and a public API for your frontends.

mini-cms schema pull and mini-cms schema push keep your local types in sync with the dashboard. The public GET /api/collections/:slug endpoint is cached, rate-limited, and ready for your Astro, Next, or Remix site.

Schema pull

mini-cms schema pull --project=acme

Public API example

GET /api/collections/projects?w=100&p=1
Illustration of a developer connecting modular blocks

Built for

Development studios that hand off content to clients.

You build the project. Your client manages the content. Mini CMS gives you a quiet dashboard for them and clean data for you.

Agencies

Portfolio projects, case studies, team bios — all structured.

Freelancers

Spin up a CMS for a client in minutes, not hours.

Internal tools

Replace spreadsheets with typed collections and an API.

Side projects

Zero monthly cost. Deploy once, run indefinitely.

FAQ

Common questions

Is Mini CMS a hosted service?
No. Mini CMS is open-source software you deploy to your own infrastructure. You provide the Turso database and the hosting target (Vercel, Cloudflare Pages, Fly.io, a VPS, etc.).
What does it cost to run?
Turso has a generous free tier (500 MB, 1 GB/month egress). Most small projects stay on the free tier. Vercel's hobby tier is also free. Total cost is effectively $0 for typical agency workloads.
Can I use it with Next.js / Astro / Remix?
Yes. The public API endpoint GET /api/collections/:slug returns JSON and works with any framework that can fetch HTTP. The CLI generates TypeScript types for your collections.
How does authentication work?
Admins create invite links sent via Resend. Recipients sign up with Better Auth and receive a dashboard role. API keys are workspace-scoped and rotate automatically.
What content types are supported?
Four field types: text, url (renders as thumbnail + modal), number, and boolean.

Ready to stop wrangling spreadsheets?

Clone the repo, add your Turso credentials, and deploy. Your first collection is live in minutes.