open source / self-hostable / Rust

jkbase.

The self-hostable Firebase alternative. Sites, server apps, functions, a managed database, and object storage — each in its own Firecracker microVM. Built in Rust.

Get Started ->

Everything you need to ship.

Nine primitives that compose into a complete platform. Deploy any kind of app — then the database, storage, and auth to back it. No vendor lock-in; runs on your own hardware.

01

Static Hosting

Deploy any static site or SPA. Push files, get an HTTPS URL. Multiple sites, prefixes, and custom domains per project. Zero configuration.

02

Server Apps

Push source in Bun, Node, Rust, Python, or Go — built server-side, no Docker on your laptop. Bring a Dockerfile if you'd rather. Persistent volumes, health checks.

03

Functions

Write Rust or JS/TS, compiled server-side to a wasi:http component. Run on request or a cron schedule. Outbound HTTP and own-bucket storage, default-deny sandboxed.

04

Managed Database

A RhypeDB instance per project — backed up automatically, reachable over TLS, with a built-in JWT issuer and default-deny per-user rules. No database to run.

05

Object Storage

S3-compatible buckets per project. SigV4 auth, presigned URLs, multipart uploads — point any AWS SDK at it. No separate service to stand up.

06

Raw UDP Services

Host a game server, voice server, or any UDP protocol. Scale to zero; the first packet wakes it. Clients connect straight to a raw port.

07

Firecracker Isolation

Every project runs in its own Firecracker microVM — a real kernel, hardware-isolated. All tenants untrusted by design. The same technology behind AWS Lambda.

08

Automatic TLS

Certificates provisioned and renewed automatically via ACME. Wildcard for project subdomains, HTTP-01 for custom domains. HTTPS everywhere, always.

09

CLI-First Workflow

Everything is a command — deploy, logs, rollback, secrets, domains — or push-to-deploy over git. Scriptable, composable, no clicking through dashboards.

From source to production.

No build pipelines to wire up. No YAML. Push source; jkbase builds it server-side and serves it on HTTPS.

01
$ jkbase project create

Create a project on jkbase.app or on a platform you host yourself. Describe it in one jkbase.toml.

02
$ jkbase deploy

Push source. jkbase builds it in a sealed, network-fenced microVM -- no Docker on your machine.

03
// live

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

Deploy in one command.

A real workflow. No tricks, no cuts.

terminal
~ $ jkbase project create my-app
created project 'my-app'
 
~/my-app $ jkbase deploy
tarring source · building in a sealed microVM
bun install · bun run build
provisioning TLS · booting microVM
 
live at https://my-app.jkbase.app

Ship something today.

Your infrastructure. Your hardware. Your rules. Open source, self-hostable, no compromises.

Open Console ->