See a change before it happens
Every create and edit shows the location’s dry run: the object it will store and the quota it will use. Nothing is written until you apply.
Local compute. Shared possibilities.
Your hardware.
A cloud your team can use.
Run containers and virtual machines on hardware you control. Give your team a simpler way to share it.
In development · Join the early-access list
Why Narabox
Your machines
Use the hardware you already own.
Your team
Share it with clear roles and quotas.
Your control
It runs on your premises, on your terms.
From spare hardware to shared infrastructure.
Connect your machines
Install Narabox from a USB stick or over the network. Your machines become a location your team can use.
Launch a workload
Containers, virtual machines and whole bare metal machines, through one console, one CLI and one API.
Invite your team
Accounts and projects with roles and quotas, so everyone gets their share and nobody steps on anyone.
Networks that do what a cloud’s do
Overlay networks, routers, floating IPs, security groups and load balancers, on your own switches.
The whole location in view
Nodes, machines, upgrades, backups and the audit log, for the people who run the hardware.
Local control
Your location
at home, in the office or in a lab
- Console, CLI and API
- Containers and virtual machines
- Bare metal machines
- Networks and load balancers
The Narabox platform
optional: one sign-in for every location you use
Cloud convenience.
Local independence.
A location is complete on its own. Join the Narabox platform to reach it from anywhere, and it keeps running when that connection drops.
- Manage locallyThe console, the CLI and the API run on the location itself.
- Choose who gets accessLocal accounts or platform accounts, with roles and quotas per project.
- Grow at your own paceStart with one machine; add nodes, networks and switches as you need them.
Secure by default, on every location.
Sharing hardware means trusting the walls between workloads. Narabox builds them in, and they’re part of every location, never a paid extra.
Containers in their own VMs
Containers never run on a node’s own kernel: each account’s containers run in a sandbox virtual machine.
Isolated networks
Each project gets its own networks, routers and security groups. One tenant’s traffic doesn’t reach another’s.
Secrets sealed to the location
Secrets are encrypted with the location’s key, and each node’s own secrets are sealed to that machine.
Locked-down nodes
No shell and no boot menu changes without a per-node password, and encryption for the data on their disks.
Encrypted backups
Backups are encrypted before they leave the location, wherever you keep them.
An audit log you can verify
Every change is recorded in a chained log, so a missing or altered entry shows up when you verify it.
Build your team’s cloud.
Help shape Narabox. Get development updates and early-access invitations.
Narabox is in development, and early access is by invitation. There’s no confirmation email yet: we’ll write when there’s something to try.