jkbase -- the self-hostable Firebase alternative

Capabilities

Everything you need to ship.

Six primitives that compose into a complete platform. No vendor lock-in. Deploy on your own hardware.

Deploy any static site or SPA. Push files, get a URL with automatic TLS. Global edge caching. Zero configuration required.

Write serverless functions in Rust or JavaScript, compiled to WebAssembly. Sub-millisecond cold starts. Scale to zero when idle.

Deploy long-running services from a Dockerfile. Persistent volumes, health checks, automatic restarts. Full control over your runtime.

Every project runs in its own Firecracker microVM. Hardware-level isolation with minimal overhead. The same technology behind AWS Lambda.

Certificates provisioned and renewed automatically via ACME. Wildcard support for project subdomains. HTTPS everywhere, always.

Everything is a command. Init, deploy, logs, rollback -- all from your terminal. Scriptable. Composable. No clicking through dashboards.

Workflow

No build pipelines. No YAML files. No waiting. Write code, deploy, done.

$ jkbase init

Scaffold a project. Pick your primitives. Generates a jkbase.toml with sensible defaults.

$ jkbase deploy

Push to production in seconds. Assets uploaded, containers built, functions compiled -- all in one command.

// live

Your project is online at your-project.jkbase.app with automatic TLS. That's it.

In practice

A real workflow. No tricks, no cuts.

terminal

~ $ mkdir my-app && cd my-app

~/my-app $ jkbase init

created jkbase.toml

created index.html

~/my-app $ jkbase deploy

uploading 2 files (4.2 KB)

provisioning TLS certificate

deploying to microVM

live at https://my-app.jkbase.app