Container isolation
Each app runs in its own container with dedicated resource limits and port boundaries, so workloads do not interfere with one another.
Enterprise
Production hosting with the controls teams need.
Isolated workloads, dedicated servers, organizations with role-based access, audit logs and deployment policies, plus hands-on help moving your stack.
- 01MembersAdmin · Developer · Viewer
- 02Audit logCSV export
- 03IP perimeter10.0.0.0/24
- 04Protected branchmain
- 05Computededicated VPS
01 / Isolation
Your workloads, kept apart.
Dedicated servers
Run on a Deployxa VPS with root access, NVMe or SSD storage and snapshots, or connect a server you already operate and deploy to it.
IP access perimeter
Restrict platform API and deployment access to approved IPv4 addresses or CIDR blocks at the organization level.
02 / Governance
Organizations, roles and an audit trail.
Organizations
Separate organizations for teams, clients or business units, each with its own projects, domains, members and billing. Switch between them from the console.
Roles and teams
Invite members as Admin, Developer or Viewer. The last admin cannot be removed and members cannot change their own role.
Audit logs
Review each member’s recent activity and export the organization audit log as CSV for your own records or reviews.
Deployment policies
Organization-wide rules such as a protected branch pattern, an allowed domain suffix and a required environment variable prefix.
Scoped API keys
Organization API keys carry only the permissions you grant, can expire, and are stored as hashes; revoke them at any time.
Billing details
Company name, billing email and address, VAT or tax ID and purchase order number on your billing documents.
03 / Support
A direct line when something needs attention.
Signed-in teams open support tickets from the dashboard, tied to their organization, so we can see the project in question. Security reports go to a dedicated address.
- Tickets from the dashboard, linked to your organization
- [email protected] for vulnerability reports
- Public status page and changelog
- 01Organizationacme
- 02Projectbilling-api
- 03Priorityhigh
- 04Statusopen
04 / Migration
Help moving what you already run.
- 01 /
Tell us what you run
Share your frameworks, databases, domains and where they are hosted today, through the contact form.
- 02 /
Plan the move
We help map each service to managed apps, databases or dedicated servers, and agree an order for the cut-over.
- 03 /
Set up the organization
Create the organization, invite your team with the right roles and set the access perimeter and deployment policies.
- 04 /
Migrate and switch DNS
Deploy each app, verify it behind health checks, then point domains at Deployxa; TLS is issued automatically.
05 / Security
Security practices, documented.
Encrypted secrets that never appear in build logs, HTTPS on every domain, health-checked rollouts and responsible disclosure are described in the trust center, alongside our privacy policy and DPA.
Secrets
Injected at build and runtime, kept out of logs.
Rollouts
Traffic moves only after health checks pass.
Disclosure
Privacy
Privacy policy, DPA and GDPR pages.
06 / FAQ
Enterprise questions.
Do you offer dedicated compute?
Yes. You can run workloads on a Deployxa VPS with root access, or connect a server you already run and deploy to it from Deployxa.
How do we control who can deploy?
Assign members the Admin, Developer or Viewer role, set a protected branch pattern for the organization, and restrict access to approved IP ranges.
Can we export audit history?
Admins can export the organization audit log as CSV from the Organization settings page, and review each member’s recent activity from the Team page.
Will you help us migrate?
Yes. Use the contact form with the Sales & enterprise topic and describe your current setup; we will work through a migration plan with you.
Ready when you are
Plan your move to Deployxa.
Tell us what you run today and what you need from a platform.