Private cloud deploy

Most teams should start with managed cloud or local mode:

Managed cloud for zero-ops workspace memory, shared API keys, billing, and support.
Local mode for one-machine privacy, no telemetry, and no signup.

Private cloud is for teams that need prxy.monster running inside their own controlled environment.

Private cloud is not a self-serve quickstart in v1. We keep the deployment path assisted so networking, provider access, storage, retention, and support boundaries are configured correctly before production traffic moves.

Use Private Cloud When

Your org requires a dedicated cloud account boundary.
You need custom networking, egress policy, or audit controls.
You need a dedicated provider-routing policy.
You need custom retention, export, or deletion rules.
You want prxy.monster support involved in production rollout.

What Stays the Same

Same API surface: /v1/messages, /v1/chat/completions, /v1/pipeline.
Same module pipeline and PRXY_PIPE config.
Same local/cloud-compatible module SDK.
Same migration path from local mode or managed cloud.

What Changes

Deployment, storage, and provider credentials live inside your controlled environment.
Workspace policy is configured during onboarding.
Release cadence and support path are coordinated with your team.
Some cloud-only features may require explicit enablement.

Start Here

Email [email protected] with:

Expected monthly request volume.
Required region or account boundary.
Provider routes you need enabled.
Data retention constraints.
Whether this is a proof-of-concept or production migration.

For a fully local setup you can run yourself today, use Local mode → Docker.