Skip to content

Private Cloud

Custom Enterprise private cloud deployments

We deploy a scalable, single-tenant Orchestrapay in a private cloud for you, in any AWS region and the availability zones you choose. Your own infrastructure, your data where it has to stay, the same API.

eu-central-1 · Frankfurt
Load balancer + WAF
Zone a
API
API
Primary
Zone b
API
API
Standby
Zone c
API
API
Your keys · encrypted at rest6 tasks across 3 zones
1
tenant per deployment: no shared servers, queues or databases
Any
AWS region, in the availability zones you choose
Multi-AZ
database with a standby ready to take over
Your keys
customer-managed encryption keys, rotated automatically

Why a private deployment

Payment infrastructure that is yours alone.

Single tenant

Your deployment runs on its own network, compute, database and message queue. No other merchant shares a server, so their traffic never slows yours.

Data residency by region

Pick the AWS region your regulator or your customers expect. Payment data, logs and backups stay in that region.

Your AWS account or ours

We deploy into a dedicated AWS account, either one you own and can audit directly, or one we run for you.

Scales with your volume

The API and workers run as container services spread across availability zones, sized for your peak and scaled out as volume grows.

Encrypted with your keys

Databases, secrets and logs are encrypted with customer-managed keys that rotate automatically.

Built to PCI DSS controls

Private subnets, a web application firewall, TLS 1.2 or higher, tamper-proof audit logs and continuous security monitoring, set up from day one.

Inside a deployment

Everything you run, and nothing you share.

Each private deployment is a complete Orchestrapay environment. Here is what it is made of.

private-cloud/eu-central-1
Edge
Load balancer, WAF, TLS 1.2+

Managed firewall rules and rate limits in front of every request.

Compute
Containers across availability zones

The API and background workers run in private subnets, spread so one zone can fail without an outage.

Data
MySQL, Multi-AZ, encrypted

Private, TLS-only, encrypted with your keys, with automated backups and a standby in a second zone.

Messaging
Dedicated message broker

Webhooks, retries and background jobs run on a queue no one else writes to.

Audit
Immutable logs

API activity and network flow logs land in a write-once log store that cannot be edited or deleted.

Monitoring
Threat detection and PCI DSS checks

Continuous threat detection, vulnerability scanning and configuration checks against the PCI DSS standard.

Never in a private deployment

  • Servers, databases or queues shared with another merchant.
  • Payment data leaving the region you chose.
  • Infrastructure changed by hand. Every change goes through reviewed code.

How it works

From a region on a map to live traffic.

01

Scope

Choose the region, the availability zones, the AWS account and the volume to plan for. We size the deployment with your team.

02

Provision

We build the whole environment from reviewed infrastructure as code, so every network rule, key and alarm is written down and repeatable.

03

Go live

Connect your processors, migrate your saved cards if you have them, and move traffic over. The API is the same one you integrate today.

Questions teams ask before they switch.

It is your own copy of Orchestrapay running on infrastructure dedicated to you, instead of the shared platform. You get the same API, routing, vault and dashboard, on servers, databases and queues that no other merchant uses.

Tell us where it needs to run.

Share the region, the availability zones and the volume you plan for. We will size a private deployment and show you what it costs.

  • Any AWS region and availability zones
  • Your AWS account or ours
  • A transparent number before you sign anything

By submitting you agree to be contacted about Orchestrapay. We never share your details.