{"slug": "spinifex-production-cloud-deployments-where-the-cloud-can-t-reach", "title": "Spinifex: Production Cloud Deployments Where the Cloud Can't Reach", "summary": "Mulga has launched Spinifex, an open-source infrastructure platform that recreates AWS services (EC2, EBS, S3, VPC, IAM) on bare-metal, edge, and on-premises environments, allowing workloads to run without hyperscalers. The platform supports unmodified AWS tooling and offers three deployment shapes: partner Neocloud, on-premises, and air-gapped edge. Key services are available now, with Bedrock AI deployment planned for Q3 2026.", "body_md": "[What is Spinifex?](#what-is-spinifex) ·\n[Platform](#the-platform) ·\n[Deploy](#three-ways-to-deploy) ·\n[AWS Compatibility](#aws-compatibility) ·\n[Components](#core-components) ·\n[Architecture](#architecture-at-a-glance) ·\n[Installation](#installation) ·\n[Docs](https://docs.mulgadc.com)\n\nSpinifex, built by [Mulga](https://mulgadc.com), recreates the AWS services your software already uses (EC2, EBS, S3, VPC, IAM) on infrastructure you control. Move workloads off the hyperscalers, run AI at a fraction of the cost, or take the cloud to the edge, without rewriting a line. The exact build you ship to AWS, Spinifex serves on your own hardware: same APIs, same Terraform, same SDKs.\n\nSpinifex 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.\n\nMost AWS alternatives wrap an API and call it a cloud. We rebuilt the engineering underneath: distributed object storage with erasure coding, block storage built to survive failure, and compute on bare metal. That depth is the reason your software runs unchanged, instead of rewritten.\n\nIt's built for teams that need:\n\n- The AWS tooling they already use (AWS CLI, SDKs, Terraform), with nothing to rewrite\n- Full control of the stack: your hardware, your network, your data, your keys\n- A cloud that keeps running offline, through disconnection, with no external control plane\n- An open core (AGPL-3.0), auditable and yours to keep, with no lock-in\n\nYou change *where* your software runs, not *what* it is.\n\nFrom commodity hardware up to unmodified AWS tooling, every layer is replaceable and yours to own.\n\nOne AWS-compatible surface, three deployment shapes. Pick the one that matches your reality; the platform on top is the same.\n\nLift and shift onto a partner Neocloud. Move workloads off the hyperscalers and onto our Neocloud partner ecosystem without rewriting them. GPU capacity (H100 / H200 / B200), cheaper, available now. Change an endpoint, keep the software.\n\nBring your own hardware and host Spinifex in your own data centre. A real multi-node HA cluster integrated with your storage and networking, with full control of stack, data, and jurisdiction. A predictable bill, no egress surprises, an auditable open-source core.\n\nCloud where the cloud can't reach. Air-gapped sites, vehicles, vessels, factories, and clinics. Compute next to the data, running through disconnection, on hardware you own. The same AWS APIs your software already uses.\n\nSpeak the AWS API surface, natively. The AWS SDKs, AWS CLI, and Terraform: everything you deploy on AWS deploys on Spinifex unchanged. At the edge, on-premise, or on a partner Neocloud.\n\n| Service | What it is | Status |\n|---|---|---|\nEC2 |\nCompute | Available |\nEBS |\nBlock Storage | Available |\nS3 |\nObject Storage | Available |\nVPC |\nNetworking | Available |\nIAM |\nIdentity & Auth | Available |\nALB / NLB |\nLoad Balancers | Available |\nEKS |\nKubernetes | Available |\nECR |\nContainer Registry | Available |\nECS |\nContainer Service | Available |\nRDS |\nDatabases | Available |\nBedrock |\nAI Deployment | Q3 2026 |\n\nRoadmap items 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](https://github.com/mulgadc/spinifex/releases).\n\nSpinifex is a minimal VM orchestration layer built on top of QEMU, exposing APIs similar to EC2. It manages lifecycle operations like start, stop, and terminate, using QEMU's QMP interface. Designed to be straightforward and scriptable, Spinifex lets you launch VMs using the AWS CLI, SDKs, or Terraform—without needing Kubernetes or heavyweight orchestrators. Keep in mind, you can also setup a Kubernetes environment using Spinifex with underlying instances.\n\n- EC2-like VM management on bare metal\n- Launches with cloud-init metadata support\n- Works with standard AWS tooling\n\n[Viperblock](https://github.com/mulgadc/viperblock) is a high-performance, WAL-backed block storage service that replicates volumes across multiple nodes. It's built for reliability and speed, with support for snapshots, recovery, and direct connection to QEMU instances using NBD or virtio-blk.\n\n- Fast, durable virtual disks\n- Replication for resilience\n- Exposed over NBD or embedded in VMs\n- Supports high performance WAL logs using local NVMe drives to reduce IO traffic to S3.\n- In memory read/write block cache for blazing performance.\n\n[Predastore](https://github.com/mulgadc/predastore) is a fully S3-compatible object storage system. It supports the AWS S3 API, including Signature V4 authentication, multipart uploads, and Terraform provisioning. Data is chunked and distributed across nodes using Reed-Solomon erasure coding, making it fault-tolerant and ideal for large-scale or low-bandwidth scenarios.\n\n- S3-compatible API and auth\n- Multipart uploads, streaming reads/writes\n- Data redundancy with Reed-Solomon encoding\n\n[Northstar](https://github.com/mulgadc/northstar) is a lightweight authoritative DNS server that handles both internal service discovery and public-facing DNS for a Spinifex cluster. Zones are human-readable TOML files, served from the local filesystem or synced from Predastore, keeping DNS configuration in the same object storage as the rest of your infrastructure.\n\n- Authoritative DNS over UDP, TCP, and DNS-over-TLS\n- Service discovery for cluster components via SRV records\n- Zone files stored locally or in S3-compatible storage\n\nEvery AWS API call is authenticated at the gateway, published to a NATS subject, and answered by whichever daemon claims it. Daemons are stateless: scale horizontally by starting more. No etcd, no Kubernetes, no external control plane. Just systemd units, a NATS cluster, and your hardware. Deep dive: .\n\n`docs/DESIGN.md`\n\n**AWS-compatible APIs.** Use the AWS CLI, SDKs, and Terraform you already know. Repoint your endpoint and ship; nothing to rewrite.**Zero cloud dependency.** Runs entirely on your hardware. No phone-home, no control plane, no external authority. Works fully offline.**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, Reed-Solomon 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 with a commercial option. Inspect it, modify it, deploy it. The platform is yours to keep.\n\nCreate a live sandbox in under a minute. The fastest way to experience the stack. Try Spinifex against one of your own workloads on infrastructure we run for you. Nothing to install, nothing to size.\n\n- Live in under a minute. No card, no install.\n- Yours for 72 hours to test and experiment.\n- Real AWS-compatible endpoint, access keys and console.\n- EC2, EBS, S3, VPC, IAM, EKS and RDS, ready to call.\n- Point your existing AWS CLI or Terraform straight at it.\n\nSignup at [https://mulgadc.com/signup](https://mulgadc.com/signup)\n\nInstallation requires an Ubuntu 26.04 or Debian 13 system. See the detailed documentation at [docs.mulgadc.com](https://docs.mulgadc.com) for installing Spinifex.\n\nThe recommended installation is a [bootable x86 installer](https://iso.mulgadc.com/spinifex.iso) for bare-metal hardware.\n\n```\ncurl -fLO https://iso.mulgadc.com/spinifex.iso\n```\n\nFollow the [USB install guide](https://docs.mulgadc.com/docs/install-usb) to write the ISO to USB and install on your hardware.\n\nPrerequisite:Spinifex requires a Linux bridge configured on the host for VM networking. See the[single-node install guide]for setup details.\n\n```\ncurl -fsSL https://install.mulgadc.com | bash\n\nsudo /usr/local/share/spinifex/setup-ovn.sh --management\n\nsudo spx admin init --node node1 --nodes 1\n\nsudo systemctl start spinifex.target\n\nexport AWS_PROFILE=spinifex\n\naws ec2 describe-instance-types\n```\n\nFor a complete development environment see the [Source Install](https://docs.mulgadc.com/docs/install-source) documentation.\n\nSpinifex coordinates these independent components:\n\n- S3-compatible object storage[Predastore](https://github.com/mulgadc/predastore)- EBS-compatible block storage[Viperblock](https://github.com/mulgadc/viperblock)- Authoritative DNS server[Northstar](https://github.com/mulgadc/northstar)\n\nEach component can be developed independently. See component-specific documentation for focused development guides.\n\nSpinifex ships with a built-in web console — an optional alternative to the AWS CLI, SDKs, and Terraform. If you're familiar with the AWS Management Console, the Spinifex UI fills the same role: a browser-based view of your instances, volumes, buckets, VPCs, and IAM resources, without leaving your own network.\n\nThe console is served by each node on port `3000`\n\nover TLS, and becomes available as soon as `spinifex.target`\n\nis up:\n\n**Same API, different surface.** Every action in the UI is the same AWS SigV4 call the CLI makes — so RBAC, audit trails, and IAM policies apply uniformly.**Single sign-on against your AWS credentials.** Log in with the access keys from`~/.aws/credentials`\n\non the node where Spinifex is installed — no separate user database.**Self-hosted, works offline.** The UI is embedded in the Spinifex binary and served from the node itself. No external CDN, no analytics calls, no cloud dependency.\n\nFor the full walkthrough — first-time TLS certificate trust, login, and feature tour — see [ Launching the Web UI](https://docs.mulgadc.com/docs/setting-up-your-cluster#7-launching-the-web-ui) in the cluster setup guide.\n\nSpinifex is developed by experienced infrastructure engineers with deep AWS expertise, including former AWS team members who understand the intricacies of building production-grade cloud services. Our team brings decades of combined experience from AWS, enterprise infrastructure, and edge computing environments.\n\n**Real-World Experience:**\n\n- Production AWS service development and operations\n- Large-scale infrastructure deployment and management\n- Edge computing and resource-constrained environments\n- Enterprise security and compliance requirements\n\nWhile Spinifex is architected and implemented by experienced engineers, we leverage **Claude Code** (Anthropic's AI coding assistant) to accelerate certain development tasks. This approach combines human expertise with AI efficiency:\n\n**How We Use Claude Code:**\n\n**Code Generation**: Boilerplate AWS API structures and handlers** Documentation**: Comprehensive development guides and API documentation** Testing**: Test case generation and validation scenarios** Refactoring**: Large-scale code restructuring and optimization\n\n**What Remains Human-Driven:**\n\n**Architecture Decisions**: Core system design and scalability choices** Security Implementation**: Authentication, encryption, and threat modeling** Performance Optimization**: Real-world performance tuning and benchmarking** Production Operations**: Deployment strategies and operational procedures\n\nThis hybrid approach ensures Spinifex benefits from both proven engineering expertise and modern development acceleration, while maintaining the quality and reliability standards required for production infrastructure.\n\n\"AWS\", \"Amazon Web Services\", and all related service names (EC2, EBS, S3, VPC, IAM, and others) are trademarks of Amazon.com, Inc. or its affiliates. Mulga Defense Corporation and Spinifex are independent and not affiliated with, endorsed by, or sponsored by Amazon.com, Inc. or Amazon Web Services, Inc. References to AWS services describe interoperability and compatibility only.\n\nSpinifex is open source under the [GNU Affero General Public License v3.0](/mulgadc/spinifex/blob/main/LICENSE). You're free to use, modify, and deploy it anywhere you need reliable infrastructure without depending on centralized cloud platforms.", "url": "https://wpnews.pro/news/spinifex-production-cloud-deployments-where-the-cloud-can-t-reach", "canonical_source": "https://github.com/mulgadc/spinifex", "published_at": "2026-08-25 00:54:43+00:00", "updated_at": "2026-08-25 01:13:06.409579+00:00", "lang": "en", "topics": ["ai-infrastructure", "ai-products", "developer-tools"], "entities": ["Mulga", "Spinifex", "AWS", "QEMU", "Viperblock"], "alternates": {"html": "https://wpnews.pro/news/spinifex-production-cloud-deployments-where-the-cloud-can-t-reach", "markdown": "https://wpnews.pro/news/spinifex-production-cloud-deployments-where-the-cloud-can-t-reach.md", "text": "https://wpnews.pro/news/spinifex-production-cloud-deployments-where-the-cloud-can-t-reach.txt", "jsonld": "https://wpnews.pro/news/spinifex-production-cloud-deployments-where-the-cloud-can-t-reach.jsonld"}}