Development environments
Protect local and shared development applications with the same access policy used in production.
Overview
A development environment is a local or shared place for building, testing, and reviewing software. It can include a laptop, virtual machine, container stack, cloud workstation, or Kubernetes namespace. It is a use pattern, not one product.
Developers need safe access to previews and internal tools without making temporary services public or adding throwaway authentication code.
Development environments supply the runtime or deployment environment. Pomerium runs in that environment and supplies the identity-aware access point for selected services.
Prerequisites
- A supported Linux host or Apple silicon Mac that can accept the user-facing route and reach the private upstream service.
- DNS, TLS, identity-provider configuration, protected secrets, and durable storage where the selected design requires it.
How it works
Run Pomerium Core on a supported Linux or macOS host in the environment. Install the official package, standalone binary, or container. Configure DNS, TLS, identity, route policy, storage, and replicas for the selected design.
Use the Pomerium quickstart or the deployment path that matches the local runtime. Give test routes valid DNS and TLS where the identity flow requires them. Keep development secrets and policy separate from production.
Check service health, DNS, TLS, required storage and replicas, and upstream reachability. Confirm that a direct public route cannot bypass Pomerium.
Example
A shared preview application runs on a private container host. Pomerium gives the engineering team one authenticated preview route and keeps the application off the broad public network.
Considerations
- A development quickstart is not a production high-availability design.
- Do not copy test credentials, signing keys, permissive policy, or local TLS shortcuts into production.
