Request access to the Spinifex sandbox. Request access
Layer_1
Spinifex V1 is released

Spinifex.

The open, AWS-compatible cloud you run yourself.

EC2, EBS, S3, VPC, IAM, on bare-metal, at the edge, or on a partner Neocloud. Workloads built for AWS run unchanged: same APIs, same Terraform, same SDKs.

Pick your deployment View on GitHub AGPL-3.0 · commercial license available
AWS compatibility

Speak the AWS API surface, natively.

AWS SDK, AWS CLI, Terraform: everything you deploy on AWS deploys on Spinifex unchanged. At the edge, on-premise, or on a partner Neocloud.

EC2
Compute
Available
EBS
Block storage
Available
S3
Object storage
Available
VPC
Networking
Available
IAM
Identity & auth
Available
ALB / NLB
Load balancers
Available
EKS
Kubernetes
Available
ECR
Container registry
Available
ECS
Container service
Available
RDS Q3 '26
Databases

Roadmap items (Q3 2026) ship under the same AWS API surface. Code written for AWS today keeps working the moment they land. Track what's shipped in the release notes.

How to run it

Two ways to deploy Spinifex.

Self-host the open-source build on your own hardware, or request a hosted environment on one of our Neocloud partners. Same platform, same APIs.

01 · Self-hosted Free · open source

Run it on your own hardware.

Bare-metal, VM, or a multi-node cluster in your data centre. AGPL, yours to keep, no phone-home.

02 · Neo-cloud Hosted · early access

Skip the install. We host it for you.

We provision a Spinifex environment on a partner Neocloud and hand you the credentials. No card, no install, just an endpoint you can point your AWS CLI or Terraform at.

  • Provisioned and managed for you
  • Same AWS-compatible APIs
  • GPU capacity available (H100 / H200 / B200)
  • Talk to a human before you commit
Request sandbox access

Reply within one business day.

Why it works

We didn't copy the API. We rebuilt the engineering underneath it.

Most AWS alternatives wrap an API and call it a cloud. We engineered the parts that are actually hard: distributed object storage with erasure coding, block storage built to survive failure, compute on bare metal. That depth is the reason your software runs unchanged, instead of rewritten.

AWS-compatible APIs

Use the AWS CLI, SDKs, and Terraform you already know. Repoint your endpoint and ship.

Zero cloud dependency

Runs entirely on your hardware. No phone-home, no control plane, no external authority.

Bare-metal compute

QEMU-based with direct hardware access. No hypervisor tax, no abstraction overhead.

Built-in storage

Block and object storage included. NVMe caching, erasure coding, and replication out of the box.

Edge-first architecture

Designed for disconnected, contested, and resource-constrained environments from day one.

Open core, no lock-in

AGPL-3.0 licensed with a commercial option. Inspect it, modify it, deploy it. The platform is yours.

The console

A real AWS-compatible cloud. Actually running.

Same EC2, EBS, VPC, S3 your software already speaks. Same console mental model your engineers already know.

Spinifex console showing EC2 instance detail running on a self-hosted Spinifex cloud
FAQ

Common questions

What is Spinifex?

Spinifex is an open-source infrastructure platform that recreates the AWS service surface (EC2, EBS, S3, VPC, IAM) on bare-metal, edge, and on-premises environments. Run cloud-native software without a hyperscaler.

Is it compatible with existing AWS tooling?

Yes. Drop-in compatible with the AWS CLI, the AWS SDKs, and Terraform. If your application talks to EC2, EBS, or S3 today, it talks to Spinifex tomorrow. No code changes required.

Does Spinifex require internet connectivity?

No. 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.

What hardware does Spinifex run on?

Any Linux-capable system, x86 or ARM. No proprietary hardware requirement. Designed for everything from rack-mounted servers to rugged edge nodes.

How does Spinifex handle storage?

Two engines. Viperblock for high-performance block storage (EBS-compatible) with snapshots, replication, and NVMe caching. Predastore for S3-compatible object storage with Reed-Solomon erasure coding, multipart uploads, and multi-node clustering. If a node is lost, objects remain available from surviving nodes, with no manual intervention.

Is Spinifex production ready?

Yes. V1 is publicly available. Core compute, block storage, and object storage services are production-ready and deployed.

What license is Spinifex under?

AGPL-3.0. The source is open and freely available. A commercial license is available for organisations that require deployment outside the terms of the AGPL.

Pick a path

Self-host today, or have us provision it for you.