Mulga
Open-source AWS-compatible cloud for running AWS workloads on any compute infrastructure without rewriting code.
Website: https://mulgadc.com/
Cover Block
Publicly reported
| Field | Value |
|---|---|
| Name | Mulga |
| Tagline | Open-source AWS-compatible cloud for running AWS workloads on any compute infrastructure without rewriting code [mulgadc.com] |
| Headquarters | Brisbane, Australia [Startup Daily, November 2026] |
| Founded | 2024 [Startup Daily, November 2026] |
| Stage | Pre-seed [PR Newswire, November 2026] |
| Business model | Open Source / Commercial [DevCuration, November 2026] |
| Industry | Deeptech |
| Technology | Software (Non-AI) |
| Geography | Oceania |
| Growth profile | Venture Scale |
| Founding team | Co-Founders (3+) [PR Newswire, November 2026] |
| Funding label | Pre-seed |
| Total disclosed | US$1.77 million [PR Newswire, November 2026] |
Links
Publicly reported
- Website: https://mulgadc.com/
- GitHub: https://github.com/mulgadc
Summary and Signal
PUBLIC Mulga is building Spinifex, an open-source, AWS-compatible cloud platform designed to let enterprises and government agencies run AWS-oriented workloads on other infrastructure without rewriting code, and it merits attention now because the company has just disclosed its first institutional financing around a product aimed squarely at cloud lock-in and sovereign deployment constraints [PR Newswire, November 2026] [Startup Daily, November 2026] [Runtime Wire, November 2026]. Founded in 2024 and based in Brisbane, with public coverage also referencing Austin, the company is early by any normal venture measure, but the timing matters: the November 2026 pre-seed round was framed around customer proofs of concept, partner integrations, and initial production deployments rather than pure product exploration [Startup Daily, November 2026] [Finsmes, November 2026] [PR Newswire, November 2026].
The product wedge is compatibility rather than a new developer paradigm. Mulga says Spinifex supports AWS APIs on infrastructure the customer controls, including bare metal, on-premises, edge, and air-gapped environments, with GitHub materials and product documentation pointing to support for familiar AWS workflows across services such as EC2, EBS, S3, VPC, IAM, EKS, and RDS [Mulga] [GitHub] [Spinifex Docs].
That positioning is more interesting because the founding team appears to have both enterprise go-to-market and AWS-native technical experience. Public reporting identifies Stuart Clout as a former thedocyard co-founder and Ansarada executive, while Ben Duncan is reported to have founded Atmail and previously worked as a principal solutions architect at AWS; coverage also places Jai Gabbard on commercial development, including US market and defense-oriented work [Startup Daily, November 2026] [Financial Times, 2021] [DevCuration, November 2026].
On financing, Mulga announced a US$1.77 million pre-seed in November 2026, led by Rally Ventures with participation from backtrace and Eastend Ventures, giving the company enough early backing to test whether open source plus commercial licensing can convert technical interest into enterprise deployments [PR Newswire, November 2026] [DevCuration, November 2026] [The SaaS News, November 2026]. One third-party profile describes Spinifex as AGPL-3.0 open-core with commercial licensing available, although that licensing detail is not fully corroborated across independent public sources and should be treated as provisional [DevCuration, November 2026].
Over the next 12 to 18 months, the main watchpoints are straightforward: whether Mulga can turn partner references and proofs of concept into named production customers, whether its AWS-compatibility claims hold up in demanding edge and air-gapped use cases, and whether the company can establish a repeatable commercial motion beyond early sovereign and infrastructure-sensitive buyers [PR Newswire, November 2026] [Runtime Wire, November 2026] [Mulga].
One source, partially checked -- Section relies on multiple public sources for company, funding, and team facts, but several product capability and licensing details remain company-sourced or only partially corroborated.
Taxonomy Snapshot
| Axis | Value |
|---|---|
| Stage | Pre-Seed |
| Business Model | Open Source / Commercial |
| Industry / Vertical | Deeptech |
| Technology Type | Software (Non-AI) |
| Geography | Oceania |
| Growth Profile | Venture Scale |
| Founding Team | Co-Founders (3+) |
| Funding | Pre-seed, total disclosed approximately US$1.77 million [PR Newswire, November 2026] |
Company Overview
PUBLIC
Mulga presents as a very new infrastructure company with a specific compatibility thesis rather than a broad cloud pitch. The company says it is building Spinifex, an AWS-compatible cloud platform intended to let customers run AWS-oriented workloads on infrastructure they control, including on-premises, edge, and alternative cloud environments [Mulga]. The available public record places the company in Brisbane, Australia, with additional public references to an Austin footprint in financing coverage, although the company website itself is the cleaner source for product framing than for corporate geography [Mulga].
The timeline that can be established from company-controlled materials is short but clear on sequence. Mulga is identified as founded in 2024 in the structured company facts provided for this report, and its website describes Spinifex as the core product and the company as focused on running AWS workloads on non-AWS compute without code rewrites [Mulga]. By 2026, the public site and related project pages positioned Spinifex around self-controlled infrastructure, including bare metal and air-gapped deployments, which suggests the company moved quickly from formation to a public product identity, even if customer adoption milestones are not yet disclosed on the website [Mulga].
No independent source found -- This section relies primarily on company-controlled web materials, with no independent state filing or Crunchbase record provided in the cited source set.
The Product and the Stack
Public record plus analysis
Mulga is selling a compatibility layer rather than a new application platform, and that distinction matters. Public materials describe Spinifex as an open-source, AWS-compatible cloud that lets enterprises and government agencies run AWS-oriented applications, scripts, and infrastructure code on infrastructure they control, including alternative public clouds, on-premises servers, and edge hardware, without rewriting code [PR Newswire, November 2026] [Startup Daily, November 2026] [Mulga, retrieved 2026]. The company’s website and GitHub materials say existing AWS CLI, SDK, and Terraform workflows can target services including EC2, EBS, S3, VPC, IAM, EKS, and RDS on customer-controlled servers, which frames the product around workload portability and reduced dependence on hyperscaler control planes rather than around a novel developer interface [GitHub - mulgadc/spinifex, retrieved 2026] [Mulga, retrieved 2026].
The technical evidence that is visible in public points to a bare-metal and edge-oriented cloud runtime with meaningful attention to networking. Spinifex documentation says the platform implements AWS-compatible VPC networking on bare metal with OVN, including public and private subnets, security groups, route tables, and Elastic IPs, while Mulga’s site says the product can run on a single node, a cluster, an edge deployment, or an air-gapped rack [Spinifex Docs, retrieved 2026] [Mulga, retrieved 2026]. Mulga also describes two deployment paths, one hosted on a partner neocloud and one self-hosted on customer hardware, and says the system is intended for environments where data sovereignty or disconnected operation rules out reliance on an external control plane [Mulga, retrieved 2026] [Runtime Wire, November 2026].
What is still less settled is the boundary between current capability and company positioning. Mulga has publicly described Spinifex 1.2.0 as a production-ready edge cloud and says v1.0 followed nine months of building in the open, but those statements are company-issued and the available coverage does not name paying customers, benchmark results, or independently verified production deployments [Mulga, retrieved 2026] [PR Newswire, November 2026]. The open-source posture appears real, with GitHub distribution and third-party reporting that the project uses an AGPL-3.0 open-core model with commercial licensing, though that licensing detail is better treated as reported than fully corroborated from primary materials alone [GitHub - mulgadc/spinifex, retrieved 2026] [DevCuration, November 2026].
No independent source found -- This section relies materially on company website, documentation, and GitHub claims, with partial support from funding coverage but limited independent verification of deployment maturity or feature performance.
The Market They Are Entering
PUBLIC
The market matters now because enterprises and public-sector buyers are under renewed pressure to reduce hyperscaler dependence without breaking AWS-based workflows, and Mulga is positioned at that point of friction rather than at the broader cloud-migration narrative [PR Newswire, November 2026] [Startup Daily, November 2026].
The immediate constraint is that no third-party TAM, SAM, or SOM for Mulga's precise category, an AWS-compatible control plane for non-AWS infrastructure, appears in the supplied public research. The safer framing is therefore adjacent-market demand, not direct market sizing. Public coverage consistently describes Spinifex as a way to run AWS-oriented applications, scripts, and infrastructure code on alternative public clouds, on-premises servers, or edge hardware without rewriting them, which implies Mulga is selling into the overlap between cloud repatriation, sovereign infrastructure, edge computing, and hybrid-cloud operations rather than a clean standalone software category [PR Newswire, November 2026] [Runtime Wire, November 2026] [DevCuration, November 2026].
That overlap is commercially meaningful because the cost of switching away from AWS is often bound up in tooling and operational habits, not only in application code. Mulga's public materials and funding coverage both center the same wedge: preserving compatibility with AWS-style APIs, CLI, SDK, and Terraform workflows on infrastructure the customer controls, whether that sits in another cloud, an on-premises environment, or an edge deployment [Mulga, retrieved 2026] [GitHub - mulgadc/spinifex, retrieved 2026] [Startup Daily, November 2026]. If that compatibility works as advertised, the addressable demand is less about greenfield cloud build-outs and more about installed AWS estates that need optionality for cost, sovereignty, resilience, or mission constraints.
The demand drivers visible in the public record are specific enough to matter even without a formal market-size report. First, cloud lock-in is the stated problem across nearly every financing write-up, with Mulga presented as an answer for buyers that want to move workloads off hyperscalers without a rewrite [PR Newswire, November 2026] [The SaaS News, November 2026] [Runtime Wire, November 2026]. Second, sovereign and disconnected environments appear repeatedly in the company's own positioning, including air-gapped and edge deployments, which suggests demand from customers operating under data-sovereignty or network-availability constraints [Mulga, retrieved 2026] [GitHub - mulgadc/spinifex, retrieved 2026]. Third, the cited deployment targets, Oracle Cloud, Cisco servers, and OnLogic edge systems, point to a buyer set that may want interoperability across public cloud, enterprise hardware, and field infrastructure rather than a single destination platform [Runtime Wire, November 2026] [Finsmes, November 2026].
The adjacent and substitute markets are clearer than the core category itself. On one side, Mulga overlaps with broader hybrid-cloud and multicloud infrastructure software, where the problem is operational consistency across mixed environments. On another, it touches edge infrastructure and private-cloud software, where control, locality, and resilience can outweigh pure elasticity. The substitute for many buyers remains a more conventional migration path: rewriting workloads for another cloud, standardizing on Kubernetes plus adjacent storage and networking layers, or accepting continued AWS concentration. Mulga's public case is strongest where those substitutes are too slow, too expensive, or incompatible with sovereign or disconnected deployment requirements [Startup Daily, November 2026] [DevCuration, November 2026] [Mulga, retrieved 2026].
Regulatory and macro forces also help explain why the timing is plausible. The company and related public profiles repeatedly reference government, defense, national-security, and data-dark operating environments, which aligns with a procurement backdrop where data residency, operational independence, and infrastructure control carry more weight than in a standard enterprise cloud sale [DevCuration, November 2026] [Jai Gabbard - Mulga Defense Corporation | LinkedIn, retrieved 2026] [Saxon Fletcher - Supabase | LinkedIn, retrieved 2026]. That does not prove government adoption, and no paying public-sector customer is named in the supplied sources, but it does indicate the regulatory frame in which Mulga is choosing to compete [PR Newswire, November 2026] [Startup Daily, November 2026].
| Market lens | Public sizing claim | Relevance to Mulga |
|---|---|---|
| AWS-compatible non-AWS cloud control plane | No named third-party sizing surfaced in supplied research | Core category remains emerging and unsized in the current source set |
| Hybrid / multicloud operations | Described in analogous terms only in supplied reporting, without third-party market figures [Startup Daily, November 2026] [DevCuration, November 2026] | Likely the closest budget line for enterprise buyers |
| Edge and sovereign infrastructure | Referenced through deployment and use-case language, not numeric market reports [Runtime Wire, November 2026] [Mulga, retrieved 2026] | Material for defense, air-gapped, and locality-sensitive use cases |
The absence of a named third-party market model is itself informative. For now, the public evidence supports a thesis of targeted demand at the intersection of hybrid cloud, edge infrastructure, and sovereignty requirements, but not a quantified claim about category scale.
One source, partially checked -- Section relies on named publisher coverage and company materials, but no independent third-party market sizing report was present in the supplied public sources.
The Competitive Field
Competitive positioning
MIXED Mulga is positioning Spinifex less as a general cloud and more as a compatibility layer for AWS-shaped workloads that need to run on infrastructure the customer controls, which places it closer to AWS-alternative control planes such as Ubicloud than to full hyperscalers themselves [Mulga, retrieved 2026] [GitHub - mulgadc/spinifex, retrieved 2026] [Startup Daily, November 2026].
| Company | Positioning | Stage / Funding | Notable Differentiator | Source |
|---|---|---|---|---|
| Mulga | Open-source, AWS-compatible cloud for running AWS-oriented workloads on alternative public clouds, on-premises servers, or edge hardware without rewriting code | Pre-seed, US$1.77M announced in November 2026 | Emphasis on AWS API compatibility across bare metal, edge, and air-gapped deployments under customer control | [PR Newswire, November 2026] [Mulga, retrieved 2026] [GitHub - mulgadc/spinifex, retrieved 2026] |
| Ubicloud | Open-source cloud platform alternative positioned around running cloud primitives on user-controlled infrastructure | Funding and stage not established in the provided research | Named competitor in the structured facts; overlap appears to be customer-controlled infrastructure rather than managed hyperscale compute | [Structured Facts] |
The segment map is narrower than a standard cloud-infrastructure category suggests. At the incumbent end sit AWS and other hyperscalers, which remain the default destination for teams already using EC2, S3, VPC, IAM, EKS, and RDS semantics, even if those providers are not framed as direct competitors in Mulga's own materials [GitHub - mulgadc/spinifex, retrieved 2026]. Adjacent substitutes are less obvious but matter: a customer can stay on AWS, refactor for another environment, or standardize around a simpler bare-metal or virtualization stack instead of preserving AWS compatibility. Mulga's bet is that compatibility itself is the wedge, especially where sovereignty, edge, or air-gapped operation narrows the feasible set of alternatives [Mulga, retrieved 2026] [Runtime Wire, November 2026].
Mulga's edge today appears to be founder-market fit plus a specific product thesis, not scale. Public reporting ties Ben Duncan to prior AWS solutions-architecture work and identifies Stuart Clout with earlier company-building and commercial experience, which is relevant for a product that must win both technical credibility and enterprise trust [Startup Daily, November 2026] [Financial Times, 2021]. The product claim that Spinifex can preserve existing AWS CLI, SDK, and Terraform workflows across user-controlled environments is also more concrete than a generic anti-lock-in pitch [GitHub - mulgadc/spinifex, retrieved 2026]. That advantage is durable only if Mulga keeps pace with the AWS surface area customers actually use. In practice, compatibility moats can be perishable, because buyers test them against real workloads rather than category narratives.
The main exposure is straightforward. Mulga is also exposed to channel concentration risk: the public record points to intended partner integrations and proofs of concept, including Oracle, Cisco, and OnLogic environments, but it does not yet identify a proprietary distribution channel or a base of named production customers that would make displacement harder [PR Newswire, November 2026] [Runtime Wire, November 2026] [Finsmes, November 2026]. If compatibility claims are the core offer, then every missing service, operational gap, or support burden becomes a competitive opening for both incumbents and adjacent substitutes.
The most plausible 18-month scenario is a bifurcated market. Mulga is the likely winner if sovereign, defense-adjacent, and edge deployments become the first repeatable use case and Spinifex proves that AWS-oriented workloads can move with low operational friction across controlled environments [Mulga, retrieved 2026] [DevCuration, November 2026]. The loser if AWS keeps tightening enterprise economics and broadening hybrid options is any young challenger whose value proposition depends mainly on cost avoidance or generalized dissatisfaction with hyperscalers, since those are easier claims for incumbents to blunt than hard technical portability.
Opportunity
PUBLIC
The prize here is unusually large for a pre-seed infrastructure company: if Mulga can make AWS portability work in production across sovereign, on-premises, and edge environments, it is selling into one of the most expensive and persistent friction points in enterprise infrastructure, namely the cost of leaving a hyperscaler without breaking the operating model built around AWS tools and APIs [PR Newswire, November 2026] [Startup Daily, November 2026].
The headline opportunity is not simply "cloud migration software." It is the chance to become a compatibility layer that lets enterprises and government agencies keep using AWS-oriented applications, Terraform, CLI workflows, and operational muscle memory while shifting workloads onto infrastructure they control or choose differently [Mulga, retrieved 2026] [GitHub - mulgadc/spinifex, retrieved 2026] [Startup Daily, November 2026]. That outcome is reachable, rather than purely aspirational, because Mulga is narrow in a useful way: the company is not claiming to outbuild AWS feature for feature, it is claiming to preserve workload compatibility across alternative environments, and the product documentation and repository both point to concrete surfaces such as EC2, EBS, S3, VPC, IAM, EKS, and RDS compatibility claims [Spinifex Docs, retrieved 2026] [GitHub - mulgadc/spinifex, retrieved 2026]. The funding announcement also frames near-term use of proceeds around proofs of concept, partner integrations, and initial production deployments, which suggests the company is aiming at operational adoption, not only developer attention [PR Newswire, November 2026] [DevCuration, November 2026].
The upside paths are still conditional, but they are legible from the public record.
| Scenario | What happens | Catalyst | Why it's plausible |
|---|---|---|---|
| Sovereign cloud control plane | Mulga becomes the preferred AWS-compatible runtime for agencies and regulated operators that need air-gapped, on-premises, or sovereignty-preserving infrastructure | A first wave of production deployments in government or defense-adjacent environments where an external control plane is operationally or legally unattractive [Mulga, retrieved 2026] [PR Newswire, November 2026] | Spinifex is described as running in standalone and air-gapped deployments, and Mulga's public messaging repeatedly targets enterprises and government agencies moving workloads off hyperscaler cloud [Mulga, retrieved 2026] [PR Newswire, November 2026] |
| Embedded layer for edge infrastructure partners | Mulga becomes bundled infrastructure software for hardware and systems partners selling edge or on-premises stacks | A deeper partner motion with vendors such as Cisco, OnLogic, or Oracle-oriented environments that reduces deployment friction [Runtime Wire, November 2026] [Finsmes, November 2026] | Public coverage already names Oracle, Cisco servers, and OnLogic systems as target environments, and Mulga says it supports both partner-hosted and self-hosted deployment paths [Runtime Wire, November 2026] [Mulga, retrieved 2026] |
| Open-source wedge into enterprise standardization | Spinifex wins developer and platform-engineering adoption first, then converts a subset into commercial support and production contracts | Continued open-source adoption after the v1.0 release and maturation of the commercial licensing motion [Mulga, retrieved 2026] [DevCuration, November 2026] | The product is publicly positioned as open source, AWS-compatible, and commercially licensable, a structure that has historically helped infrastructure vendors land technical users before broader enterprise procurement [DevCuration, November 2026] [GitHub - mulgadc/spinifex, retrieved 2026] |
What compounding could look like is relatively clear even if it is early. One successful deployment should make the next one easier because the core promise is portability: if a customer can use the same AWS-oriented scripts, images, and infrastructure-as-code across AWS, alternative clouds, on-premises servers, and edge hardware, then each validated environment broadens the set of adjacent workloads Mulga can credibly support [Mulga, retrieved 2026] [GitHub - mulgadc/spinifex, retrieved 2026]. The flywheel is product credibility rather than a consumer-style network effect. Every proof point that Spinifex preserves familiar AWS workflows in a new environment reduces switching risk for the next buyer, and every partner integration broadens distribution without requiring Mulga to own the full hardware stack [PR Newswire, November 2026] [Runtime Wire, November 2026]. If the open-source footprint grows alongside that, the company could benefit from a standard open-core pattern in which community adoption lowers customer acquisition friction and commercial support captures the highest-stakes production use cases [DevCuration, November 2026].
The size of the win is best framed through a comparable already named in Mulga's competitive set. If Mulga were to become a credible sovereign and edge-oriented AWS compatibility platform, the outcome could reasonably map to a venture-scale infrastructure business worth hundreds of millions of dollars or more at maturity (scenario, not a forecast), particularly because the company is positioned against hyperscaler dependence rather than inside a narrow point-solution niche [Startup Daily, November 2026] [PR Newswire, November 2026]. Public sources here do not support a tighter valuation analog, so the prudent read is that the upside is category-sized, but the quantitative ceiling remains under-evidenced at this stage.
Thinly sourced -- Section relies on one independently reported funding event, several company and repository product claims, and limited third-party corroboration of commercial traction.
Sources
Publicly reported
[mulgadc.com] Mulga | Run AWS workloads on any compute, zero re-write | https://mulgadc.com/
[Startup Daily, November 2026] Queensland cloud migration startup Mulga grabs $2.6 million pre-Seed | https://www.startupdaily.net/topic/funding/queensland-cloud-migration-startup-mulga-grabs-2-6-million-pre-seed/
[PR Newswire, November 2026] Mulga Raises US$1.77 Million in Pre-Seed Funding to Help Enterprises and Governments Move Workloads Off Hyperscaler Cloud | https://www.prnewswire.com/news-releases/mulga-raises-us1-77-million-in-pre-seed-funding-to-help-enterprises-and-governments-move-workloads-off-hyperscaler-cloud-302941321.html
[DevCuration, November 2026] Mulga Raises US$1.77M Pre-Seed for AWS-Compatible Cloud | https://devcuration.com/articles/mulga-raises-us1-77m-pre-seed-aws-compatible-cloud
[Finsmes, November 2026] Mulga Raises $1.77M in Pre-Seed Funding | https://www.finsmes.com/2026/11/mulga-raises-1-77m-in-pre-seed-funding.html
[Runtime Wire, November 2026] Mulga raises $1.77M for Spinifex, built to move AWS-oriented workloads elsewhere | https://runtimewire.com/article/mulga-raises-1-77m-to-let-aws-workloads-leave-aws-without-a-rewrite
[GitHub] mulgadc | GitHub | https://github.com/mulgadc
[Spinifex Docs] Spinifex Docs: AWS-Compatible Bare-Metal Cloud Platform | https://docs.mulgadc.com/
[Mulga] Mulga | Run AWS workloads on any compute, zero re-write | https://mulgadc.com/
[Financial Times, 2021] The quest for M&A green value | https://www.ft.com/partnercontent/ansarada/the-quest-for-m-and-a-green-value.html
[The SaaS News, November 2026] Mulga Raises $1.77M Pre-seed | https://www.thesaasnews.com/news/mulga-raises-1-77m-pre-seed/
[GitHub - mulgadc/spinifex] spinifex | GitHub | https://github.com/mulgadc/spinifex
[Jai Gabbard - Mulga Defense Corporation | LinkedIn] Jai Gabbard - Mulga Defense Corporation | LinkedIn | https://www.linkedin.com/
[Saxon Fletcher - Supabase | LinkedIn] Saxon Fletcher - Supabase | LinkedIn | https://www.linkedin.com/
Articles about Mulga
- Mulga Gives AWS Workloads a Passport to Any Server, Anywhere — The Brisbane startup's Spinifex platform lets government and enterprise code run on any infrastructure, from hyperscalers to air-gapped defense systems.