Core Concepts - Replov Docs
Skip to main content

Core Concepts

Understanding the fundamental concepts of Replov will help you make the most of the platform.

Projects

What is a Project?

A project is a container for related services. It's linked to a GitHub repository and helps you organize your deployments.

  • • One project = One GitHub repository
  • • Multiple services can belong to one project
  • • Shared environment variables across services
  • • Unified deployment history
Think of a project as your application. For example, a "Blog" project might contain a Static Site (frontend), Web Service (API), and Background Worker (email sender).

Services

Core Service Types

Each service type is optimized for a specific use case:

• Web Service - Public HTTP apps
• Static Site - Nginx-served static projects
• Redis - Persistent managed datastore
• Private Service - Internal only
• Background Worker - Job processing
• Cron Job - Scheduled tasks
• Vitibase - Separate PostgreSQL backend platform

Deployments

Dashboard Deployments

A deployment uses the repository and branch configured on the service:

  1. 1. Push the commit you want to your configured branch
  2. 2. Start a deployment from the Replov dashboard, or let Auto Deploy start it on the push
  3. 3. Replov clones the source and builds a Docker image
  4. 4. The Docker service is created or updated
  5. 5. Review deployment status, health, and logs
With Auto Deploy on, each push to the service's branch deploys automatically. Updating or recreating a service can briefly interrupt traffic.

Environment Variables

Environment variables are key-value pairs that configure your application:

  • Secure: Encrypted at rest and in transit
  • Project-level: Shared across all services in a project
  • Service-level: Specific to individual services
Never commit secrets to your repository. Always use environment variables for API keys, database passwords, and other sensitive data.

Billing & Plans

Two Billing Models

Hourly Billing

Pay only for the hours your service runs. Perfect for development and testing.

Monthly Billing

Flat monthly rate for 24/7 services. Save ~2% compared to hourly for always-on services.

Regions & Infrastructure

All services are deployed in our primary region with:

  • • Compute tiers: Manual CPU and memory plan changes
  • • Ingress routing: Traefik routes public hostnames to the selected service
  • • Health checks: Automatic restart if service becomes unhealthy
  • • SSL/TLS: Free HTTPS certificates for all services

Internal Networking

Services within the same project can communicate using internal hostnames:

service-name.Replov-network
Internal communication is free and doesn't count toward bandwidth limits. Always use internal hostnames for service-to-service communication.

Next Steps