The AIOX SaaS at app.aioxsuite.com works for the vast majority of customers. But some operators — enterprises with data-residency requirements, agencies serving regulated industries, governments — need to host AIOX themselves. That option exists. Here’s the practical guide.
Same code, your infrastructure
The core AIOX server is a WordPress plugin (the same one that powers app.aioxsuite.com). It deploys on a standard WordPress + MySQL stack. There’s no separate “self-hosted edition” or feature-gated build — it’s the same code, the same updates, the same support.
The customer-side Suite plugin connects to whatever URL your self-hosted server lives at. So your customers’ WordPress sites talk to aiox.yourdomain.com instead of app.aioxsuite.com. Everything else works identically.
Why operators choose self-hosting
- Data residency — content must stay within a specific jurisdiction (EU, China, regulated US sectors).
- Compliance frameworks — HIPAA, FedRAMP, ITAR, certain sector-specific regulations that require dedicated infrastructure.
- Integration constraints — must integrate with internal SSO, internal observability, internal billing platforms.
- Reseller business model — you want to white-label and sell to your own customers under your brand and infrastructure.
- Cost — at extreme scale, self-hosting beats SaaS pricing. Not common, but real.
Deployment options
- Your own AWS / GCP / Azure — a Terraform / Ansible blueprint provided. Standard WordPress deployment with a few AIOX-specific extras.
- On-prem datacentre — same plugin, same DB schema. We support this with explicit guidance.
- Hybrid — self-hosted control plane, AI inference outsourced to your preferred provider (OpenAI, Anthropic, Google, self-hosted Llama). The AI provider is operator-configurable.
What’s different from SaaS
- You provide the LLM API key (Gemini / OpenAI / Anthropic) directly. Per-token costs flow to your bill from the provider, not via AIOX.
- You handle WordPress updates, backups, security patches yourself (or via your IT). Standard sysadmin work.
- You get the same code that runs our SaaS — including every app and every dashboard tab.
- Support model differs: enterprise contracts include dedicated support engineers; self-hosted customers on standard licensing use community support + paid escalation if needed.
Licensing model
Self-hosting is GPL — same as WordPress itself. You can deploy as many instances as you want without per-instance fees. Enterprise plans add commercial support, SLA, and dedicated engineering time. Pricing scales with deployment scope (single instance vs multi-tenant white-label).
Upgrade path
Updates flow the same way as for the SaaS: new versions are published to a private update channel; you fetch and deploy on your schedule. Major upgrades (1.x → 2.x) follow standard semver — backwards-compatible by default; breaking changes published as RFCs ahead of release.
How to start
Contact us. The conversation starts with: what’s driving the self-host decision, what’s your target deployment timeline, what compliance frameworks do you need to satisfy. We respond within one business day.
