Open Source AWS Outposts Alternatives
A curated collection of the 2 best open source alternatives to AWS Outposts.
The best open source alternative to AWS Outposts is OpenStack. If that doesn't suit you, we've compiled a ranked list of other open source AWS Outposts alternatives to help you find a suitable replacement. Other interesting open source alternative to AWS Outposts is Spinifex.
AWS Outposts alternatives are mainly Cloud Infrastructure Management but may also be Storage Solutions. Browse these if you want a narrower list of alternatives or looking for a specific functionality of AWS Outposts.
Interoperable components providing computing, networking, and storage resources through programmable APIs, for organizations that run their own cloud.
OpenStack is a collection of interoperable components that can be deployed together to provide computing, networking, and storage resources. Once deployed, those resources are reached by end users through programmable APIs rather than a fixed console.
This particular repository is not that code. It represents OpenStack as a collection of git submodules, with the repositories for individual components hosted separately, and it is intended to be used in a read-only manner.
The superproject exists to answer a question that is otherwise awkward to answer.
- Tested combinations: any commit here points at a set of component commits that were explicitly tested with each other.
- Zuul gating: the continuous integration system gates all contained projects in an effective single timeline.
- Submodule tracking: Gerrit updates the superproject whenever a subproject changes, capturing the sequence Zuul produced.
- Component sources: the working repositories for each component live in the OpenStack namespace on opendev.
- Read-only intent: commits are not made here directly, since the superproject records history rather than holding it.
Anyone who needs to pin a deployment to a known-good combination of component versions can take it from here instead of reconstructing it commit by commit across every project. Documentation for the individual components, the contributor process, and the governance model is maintained separately by the OpenStack community.
An AWS-compatible cloud platform for teams running EC2, S3, VPC and IAM workloads on their own bare metal, edge or Neocloud hardware.
Spinifex recreates the AWS service surface on infrastructure you control. Software written for EC2, EBS, S3, VPC and IAM keeps working unchanged, because the AWS CLI, the SDKs and Terraform talk to Spinifex the way they talk to AWS. What changes is where the workload runs, not what it is.
Every API call is authenticated at a gateway, published to a NATS subject and answered by whichever daemon claims it. Daemons hold no state, so scaling out means starting more. There is no etcd, no Kubernetes and no external control plane, so a cluster keeps serving through disconnection.
The platform is assembled from several Go services and the open source pieces around them.
- Spinifex: VM orchestration over QEMU driven through the QMP interface, with EKS, ECS, ECR and RDS built on that same instance layer.
- Viperblock: block storage with write ahead logs on local NVMe, replicated across nodes and exposed over NBD or virtio-blk.
- Predastore: S3 compatible object storage with SigV4 auth, multipart uploads and Reed-Solomon erasure coding across nodes.
- Northstar: authoritative DNS for cluster service discovery and public records, with zones kept as readable TOML files.
- Networking: OVN backs VPC networking and security groups, while HAProxy and nginx serve the load balancer APIs.
The same platform deploys in three shapes, a partner Neocloud with GPU capacity, a multi-node cluster in your own data center, or an edge site running air gapped. It is Go and AGPL 3.0, with a 72 hour hosted sandbox for pointing an existing workload at it first.
