Region Falkenberg · operational
Our own stack · our own hardware · 100% renewable Nordic power
Trust Docs Changelog
Log in → ENSV
Platform · signature primitive

A Planet is your entire infrastructure in one object.

Hyperscalers give you 200 services and a consulting engagement. Kepler gives you a Planet: OpenStack’s engine wrapped in the Kepler layer, fused into an isolated part of the cloud that is entirely yours.

Spin up a Planet Capabilities →
The anatomy

The engine + the layer = Planet.

Data plane

OpenStack (the engine)

  • Nova — compute / VMs
  • Neutron — SDN, networking, floating IP
  • Cinder — block volumes & snapshots
  • Glance — curated OS images
+
fuserat
Control plane

The Kepler layer (the experience)

  • Laravel/Octane + Temporal orchestration
  • OpenBao — per-tenant credential isolation
  • Logto — identity, teams & RBAC
  • Next.js console + idempotent REST API

A Planet = your isolated slice of Kepler in a region

Your own tenant project, your own network, your own storage and your own credentials — lazily provisioned the first time you use the region. Concrete, sellable and architecturally honest: it maps directly to one OpenStack project per tenant per region.

Who does what

We run the foundation. You control your Planet.

Kepler runs

The control plane & the engine

  • OpenStack operations: Nova, Neutron, Cinder, Glance
  • The hardware — our own servers in Falkenberg
  • Per-tenant isolation & credential rotation (OpenBao)
  • Quota enforcement & async audit log
  • Patching, monitoring, capacity
You're in control

Your Planet via console & API

  • VMs: create, resize, snapshot, start/stop
  • Networking: VPC, routers, NAT, floating IPs, security groups
  • Storage: block volumes, snapshots, restore
  • Teams, roles, API keys
  • All via REST API + Terraform — or the console
Security proof

Isolation you can verify, not just read about.

Every tenant gets its own OpenStack project and its own credentials, managed and rotated by OpenBao. No shared keys, no passive coexistence. This is a checkable item in a procurement — not a marketing phrase.

per-tenant isolation
# Varje tenant → eget projekt + egna credentials
tenant_acme   → openstack_project: "kepler-acme-swe1"
              → creds via OpenBao (roterade, aldrig delade)
tenant_globex → openstack_project: "kepler-globex-swe1"
              → creds via OpenBao (isolerad fail-domain)

Maps directly to tenant_openstack_projects — one project per tenant per region, lazily provisioned on first use.

Available now

Three primitives, all in production today.

Compute Now

VMs, flavors, curated images, noVNC console, SSH keys, boot-from-volume.

Compute

Networking Now

Provider networks, VPC, routers, NAT gateway, floating IP, security groups.

Networking

Storage Now

Block volumes, volume and server snapshots, attach/resize/restore.

Storage

Control your Planet from anywhere.

Console, CLI and API — the same control surface, the same names for everything. What you click in the console, you can script in the pipeline.

Start building Documentation
Console · CLI · REST API

Connected to everything.

Terraform and REST API today. GitDeploy for GitHub & GitLab in beta. Lovable exports get a home on a Planet.

Capabilities Try now
+ more integrations on the roadmap
Tell us what you're building — an engineer replies within 4 hours (weekdays) and sketches your architecture for free. Whether or not you become a customer. Book an architect call →

Spin up your first Planet.

Your own cloud in Falkenberg in minutes — compute, networking, storage and a console, all yours.

Start building See pricing