Deploy Presenton On-Premise

On‑premise (self‑hosted) deployment lets you run Presenton within your own network and infrastructure, so content, templates, and logs stay under your control. It’s ideal for organizations with strict privacy, regulatory, or residency requirements.

Organizations that require strict data governance, private networks (including air‑gapped), custom security controls, or integration with internal identity providers typically choose on‑premise. If you want zero infrastructure management and fastest time‑to‑value, the cloud is a great fit.

All data remains within your environment. You choose storage, access controls, and network boundaries. Role‑based access, auditability, and encryption in transit are supported. You can optionally restrict outbound traffic or run in an isolated/air‑gapped network.

Deployments can be configured to support common frameworks such as GDPR and SOC 2.You retain control over data retention, backups, logging, and access, helping you align with your internal policies and external requirements.

Containerized deployment is recommended (Docker/Kubernetes). Typical starter sizing: 4–8 vCPU, 16–32 GB RAM, and fast SSD storage; scale horizontally for higher throughput. External PostgreSQL and object storage are commonly used in production.

Yes. Images can be mirrored to an internal registry and deployed without internet access. If you use external AI providers, disable them or route through approved internal services.

Single sign‑on via SAML/OIDC is supported, along with API keys for service integrations. Many teams integrate with providers like Okta, Azure AD, or Keycloak for centralized access control.

Yes. You can connect to local or private AI endpoints, or selectively enable external providers (e.g., Azure OpenAI) for non‑sensitive tasks. Model routing is configurable per environment.

We provide versioned images and release notes. You can update via Helm/manifests with controlled rollouts. For offline sites, updates can be staged through an internal registry following your change‑management process.

Yes. Content, templates, and settings can be exported/imported to ease migration in either direction. Many customers prototype in cloud, then move to on‑premise as they scale.

Yes. Enterprise plans include priority support, SLAs, and onboarding assistance. Talk to our team to tailor support to your environment and risk posture.

On‑premise is licensed for production and non‑production environments with usage tiers. Contact us to discuss your team size, throughput, and security needs.