Zero-config builds
Node, Python, Go, Ruby, PHP, Rust, Java and static sites detected automatically. Bring a Dockerfile and we'll use it instead — your build, your rules.
New Perth (ap-au-west-1) is now generally available
One command from repository to production.
Neoxa deploys your apps, databases and background workers onto infrastructure you own — in Sydney, Melbourne and Perth. No control plane offshore. No data leaving the country. No Kubernetes to learn.
Free while you evaluate · Bring your own servers or ours · Australian-owned and operated
~/acme-api $ neoxa deploy→ Detected Node 22 · Fastify · binds 0.0.0.0:3000→ Building linux/amd64 image ……… 11.4s→ Provisioning postgres-16 ………… 4.1s→ Injecting DATABASE_URL into acme-api→ Rolling out to syd-1 · 2 replicas · health OK✓ Live https://acme-api.neoxa.au (22.3s)✓ Certificate issued · TLSv1.3 · data resident in AU
Built for teams that cannot send data offshore
How it works
Three steps. No YAML in sight.
Point Neoxa at a repository. It reads your stack, builds the image, provisions what the app needs and puts it behind TLS — on your own compute.
01
Connect
Link a Git repository or push an image you already build. Neoxa detects the runtime, the port it binds to, and the environment variables it expects — then tells you what it found before anything runs.
02
Provision
Need Postgres, Redis or object storage? Declare it once. Neoxa provisions it inside your namespace, wires the connection string into the app as DATABASE_URL, and takes nightly snapshots that never leave your region.
03
Deploy
Run neoxa deploy. You get a health-checked rollout, a signed certificate, logs and metrics — and a one-click rollback to the previous release if anything looks wrong.
Capabilities
Everything the app needs, nothing it doesn't.
Managed data layer
Postgres, MySQL, MongoDB, Redis and ClickHouse provisioned in a click, with automated backups, point-in-time restore and credentials injected straight into your services.
Workers & schedules
Queue consumers, cron jobs and long-running workers deploy alongside your web service and scale independently — with the same logs and the same rollback.
Private by default
Every app starts closed. Open it to the internet, to an IP allow-list, or to your VPN only. Secrets are encrypted at rest and never printed in a build log.
Logs & metrics included
Streaming logs, CPU and memory per replica, request latency and deploy history — in the console and on the CLI. No separate observability bill.
CI/CD in one file
Generate a GitHub Actions workflow that builds, uploads and releases to the same app on every merge — without changing the URL your customers already use.
Data sovereignty
Your data stays on the continent.
Compute, storage, backups, logs and the control plane all run inside Australia. There is no offshore region to fail over to, because there is no offshore region. Designed to sit comfortably inside the Essential Eight and Australian Privacy Principles your auditors already ask about.
Sydney ap-au-east-1 Operational
Melbourne ap-au-south-1 Operational
Perth ap-au-west-1 Operational
3
Australian regions, no offshore failover
0
Bytes of customer data stored outside AU
1
Command from clean checkout to live URL
24/7
Support staffed in Australian hours
The engine room
Neoxa runs on PlugLayer.
We didn't rebuild orchestration from scratch. Neoxa is the Australian surface on top of PlugLayer — the deployment layer that turns any server you own into a managed platform, and hands the keys back to you.
LAYER 01
Your compute
A bare-metal box in a Sydney rack, a VM at an Australian provider, or hardware in your own comms room. You own it; we schedule onto it.
LAYER 02
PlugLayer core
Attaches nodes, carves per-project namespaces, mirrors images, manages storage and rolls out releases with health gates and instant rollback.
LAYER 03
Data layer
One-click databases from vetted templates, with credentials synced into dependent apps automatically — no copy-pasting connection strings.
LAYER 04
Neoxa
The CLI, the console, the routing, the certificates and the Australian support desk that turns all of it into a single command.
Pricing
Priced per node, not per surprise.
You pay for the platform, not for egress, seats, build minutes or the privilege of reading your own logs.
Solo
A$0
For evaluating Neoxa and shipping side projects.
Start free- One project, three apps
- Shared compute in Sydney
- Managed Postgres or Redis
- Automatic TLS and subdomain
- Community support
Team
Most popularA$180 / node / month
For product teams running real customer workloads.
Start deploying- Unlimited projects and apps
- Dedicated nodes in any AU region
- Custom domains and wildcard certs
- GitHub Actions CI/CD, preview builds
- Nightly backups, 30-day retention
- Email and Slack support, AEST hours
Sovereign
Talk to us
For regulated, air-gapped and government workloads.
Contact sales- Deploy into your own datacentre
- SSO, SCIM and granular RBAC
- Audit logging and change evidence
- Disaster recovery with tested restores
- Named engineer and onboarding
- Contracted response-time SLA
Questions
The things people ask first.
Do I have to know Kubernetes?
No. Neoxa runs a managed control plane on your nodes and exposes apps, databases and workers as first-class objects. You describe what you want in plain terms; there is no cluster to babysit and no manifest to hand-write. If you already know Kubernetes, the escape hatches are there when you need them.
Can I bring my own servers?
Yes — that's the point. Attach a machine over SSH and it becomes schedulable compute in minutes, whether it lives in a Sydney colocation facility, at an Australian cloud provider, or in your own building. If you'd rather not source hardware, you can rent dedicated nodes from us in any of the three regions.
What actually stays in Australia?
Application containers, persistent volumes, database storage, backups, build artefacts, logs, metrics and the control plane itself. Support access is performed by Australian-based staff. The only traffic that crosses a border is traffic your own application chooses to send.
How do rollbacks work?
Every release is an immutable image plus the configuration that shipped with it. Rollout is health-gated, so a container that fails its readiness check never takes traffic. Rolling back selects a previous release and redeploys it — the URL, certificates and attached data all stay exactly where they were.
What happens if we outgrow Neoxa?
You keep everything. The images are standard OCI, the databases are stock upstream engines, and the volumes are yours on hardware you control. There is no proprietary runtime to unpick and no export queue to join — leaving is a matter of pointing DNS somewhere else.
Is there a free trial?
The Solo tier is free for as long as you want it, including a managed database and a TLS subdomain. Team is billed per node, monthly, with no lock-in — cancel and your workloads keep running until the end of the period.
Put it in production this afternoon.
Attach a node, point Neoxa at your repository, and watch it go live on infrastructure you own — without a single line of YAML.