Lahijan
Open source · Self-hosted

Your cloud, your rules.

Compute, DNS, and object storage behind one clean self-service portal. Deploy in minutes with a single command.

Self-host LahijanRead the docs

MIT licensed · One binary · Docker Compose

What your users get

Compute
System containers and virtual machines
DNS
Authoritative zones and records
Object storage
S3-compatible buckets and keys
Extensions
Sandboxed WASM, installed as .lahx

Get started in one command

Terminal
# clone, configure, bring the stack up
docker compose up -d
Go binary. One process, no microservices to wire together.
1
Core services: compute, DNS and object storage.
3
Seconds per metering tick. Every resource bills by the minute.
60
Languages from day one, right-to-left included.
2

Platform

Everything you need to run a cloud

Three best-of-breed backends, one unified control plane, zero vendor lock-in.

Workflow

How it works

One platform, three concerns, a single deploy.

  1. Deploy

    Run docker compose up. Lahijan brings up its database and the three backends it wraps.

  2. Onboard

    Invite users, set their quotas, and top up their balance. They get a self-service portal for compute, DNS, and S3.

  3. Scale

    Every resource meters per minute. The ledger records every credit and debit; receipts are a query away.

Architecture

Architecture at a glance

A monolithic control plane over three focused backends.

  1. 01 / Client

    End user (browser)

    REST/JSON for control; S3 direct for data.

  2. 02 / Control plane

    Lahijan backend (Go)

    One GoFiber monolith. REST API, services, repository layer, job queue, WASM runtime.

  3. 03 / State

    PostgreSQL

    Shared by Lahijan and the backends. Row-level tenant isolation.

  4. 04 / Services

    Compute · DNS · Object storage

    Three best-of-breed backends, abstracted behind the Lahijan API.

Pricing

You set the prices

Lahijan is free and open source, and there is no hosted version. Operators name their own prices; Lahijan meters usage and keeps the ledger.

Compute
per vCPU-hour
Metered per minute while an instance is running, priced per vCPU-hour in your catalog.
DNS zones
per zone-month
Metered per hosted zone per month.
Object storage
per GB-month
Metered per GB stored per month; egress metered per GB.

Lahijan has no price list of its own. Each operator sets the catalog for their deployment under Administration > Billing.

Documentation

Everything is written down.

Guides for the people using a Lahijan deployment, and references for the operators who run one. Every setting, endpoint and permission is listed.

Read the docs

FAQ

Frequently asked questions

Short answers to the questions operators ask first.

Can I self-host Lahijan?

Yes. The whole stack (Lahijan, its database and the three backends) runs from one docker compose file.

Which backends does Lahijan use?

Lahijan wraps three mature open-source projects for compute, DNS, and object storage. They are abstracted behind the Lahijan API; end users never see their names.

Is Lahijan multi-tenant?

Yes. Every row in the database carries a tenant id, enforced at the repository layer. Tenants cannot see each other's data.

How does pricing work?

Each operator sets their own unit prices. Users prepay into a balance; usage is metered per minute and debited from the ledger.

What are WASM extensions?

WebAssembly modules, packaged as .lahx files, that add new automation to Lahijan. Each extension declares a permission manifest, and an admin approves every permission at install time.

Is there an API?

Yes. Every action you can do in the UI you can do over a versioned REST API with generated client libraries.

Get started

Run your own cloud today.

Clone the repo, edit the config, bring the stack up. That's it.

Free and open source. No account, no credit card.

Self-host LahijanRead the docs