Networking - Replov Docs
Skip to main content

Networking

Public HTTPS routing, custom domains, and private project networking

Replov runs its core workloads on the current DigitalOcean infrastructure. Traefik routes public web and static services, while private services stay off the public ingress and communicate on their project network.

Public services

Generated domain

Each deployed web or static service receives a stable generated hostname.

https://service-name-hash.replov.com

Managed HTTPS

Traefik terminates HTTPS for generated and verified custom domains. Certificate issuance can take a few minutes after DNS becomes valid.

Regional ingress
Replov does not currently provide a global CDN. Add an external CDN or WAF in front of your service when your application requires global edge caching or additional network filtering.

Custom domains

  1. 1

    Add the domain

    Open the service Domains screen and enter the hostname you control.

  2. 2

    Copy the DNS target

    Use the exact DNS target shown by Replov; do not guess the base domain or server IP.

  3. 3

    Update DNS

    Create the requested record with your DNS provider and wait for propagation.

  4. 4

    Verify and activate

    Run verification from the dashboard. Routing and TLS are enabled only after the ownership and DNS checks pass.

DNS values are environment-specific
Always use the target displayed in the dashboard. Replov validates the hostname and rejects domains that are already attached to another service.

Private services

Private services do not receive a public route. Services in the same project network can connect using the internal service name and the port exposed by the target container. Keep credentials in environment variables rather than committing them to your repository.

Example internal connection

http://orders-worker:3000

Replace both values with the service name and port configured in your project.

Current limits

  • Deployments and plan changes may briefly interrupt traffic.
  • Multi-instance load balancing, sticky sessions, and automatic failover are not part of the current core service.
  • IP allowlists and application rate limits must be implemented in your app or external edge provider.
  • Only web and static services receive public ingress; workers and cron jobs do not.