Open-source AWS-compatible platform for secure edge deployments.
Your infrastructure. Your hardware.
Zero cloud dependency.
Built for environments where running in the cloud isn't an option. Whether you're deploying to edge sites, private data-centres, or operating in low-connectivity or highly contested environments — Spinifex gives you EC2-style compute, EBS-compatible block storage, and S3-compatible object storage on your own hardware.
Three services. One platform.
Complete edge infrastructure.
EC2-compatible VM orchestration built on QEMU. Launch instances with the AWS CLI, SDKs, or Terraform. Cloud-init metadata, instance types, and full lifecycle management.
EBS-compatible block storage with WAL backing, replication, snapshots, NVMe caching, and in-memory read/write optimisation. Attach volumes via NBD or virtio-blk.
S3-compatible object storage with Signature V4 auth, multipart uploads, and Reed-Solomon erasure coding for fault tolerance across nodes.
Up and running in minutes
Single command install on any Ubuntu/Debian system.
$ curl -fsSL https://install.mulgadc.com | bashConfigure OVN for VPC networking and virtual machine connectivity.
$ sudo /usr/local/share/spinifex/setup-ovn.sh --managementBootstrap the local control plane.
$ sudo spx admin init --node node1 --nodes 1Start the Spinifex services.
$ sudo systemctl start spinifex.targetUse the standard AWS CLI to query available EC2 instance types to launch.
$ export AWS_PROFILE=spinifex
$ aws ec2 describe-instance-typesCongratulations the Spinifex environment is initialized. Next, view our documentation on creating VPCs, subnets, installing AMI images, launching instances and more.
The cloud isn't always an option
Edge sites, private data-centres, air-gapped networks, contested environments — Spinifex delivers full-stack infrastructure wherever you need it.
Use the AWS CLI, SDKs, and Terraform you already know. No new tooling, no rewrites.
Runs entirely on your hardware. No phone-home, no control plane, no external authority.
QEMU-based compute with direct hardware access. No hypervisor tax, no abstraction overhead.
Block and object storage included. NVMe caching, erasure coding, replication—out of the box.
Designed for disconnected, contested, and resource-constrained environments from day one.
AGPL-3.0 licensed with a commercial option available. Inspect, modify, and deploy without vendor lock-in.
What you get out of the box
Spinifex is open source and publicly available as a V1 release. Try it on your own hardware, or get in touch to discuss deployment at scale.
Spinifex is an open-source infrastructure platform that replicates core AWS services for bare-metal, edge, and on-premises environments. It lets you run cloud-like compute, storage, and object storage without depending on centralised cloud providers.
Yes. Spinifex provides drop-in compatibility with the AWS CLI, SDKs, and Terraform. If your application works with EC2, EBS, or S3—it works with Spinifex, no code changes required.
No. Spinifex is designed to operate fully offline. Every service runs locally on your hardware with zero dependency on external networks or cloud control planes. Connectivity is optional, not required.
Spinifex runs on any Linux-capable system—x86 or ARM. There is no proprietary hardware requirement. It is designed for everything from rack-mounted servers to rugged edge nodes.
Spinifex includes two storage engines: Viperblock for high-performance block storage (EBS-compatible) with snapshots, replication, and NVMe caching; and Predastore for S3-compatible object storage with Reed-Solomon erasure coding, multipart uploads, and multi-node clustering. Predastore distributes data across nodes for resilience and automatic failover—if a node is lost, objects remain available from surviving nodes without manual intervention.
Spinifex is now publicly available as a V1 release. Core compute, block storage, and object storage services are production-ready and available for deployment.
AGPL-3.0. The source is open and freely available. A commercial license is also available for organisations that require deployment outside the terms of the AGPL.