MANAGED CONTAINERS, ON YOUR SERVERS

Easily deploy
managed apps and databases

Focus on your product, not on your infrastructure. Upvale is a product for developers who want the ease of use of managed container apps and databases, without the cost of it.

Upvale showing the Application Playground project, its applications, databases and scheduled job, with the workspace navigation sidebar.Upvale in dark mode showing the Application Playground project, its applications, databases and scheduled job, with the workspace navigation sidebar.
Inside a project · Workspace view
Simple setup No per-app fee Compose when you need it

01 / SERVICES

Apps, databases
and scheduled jobs.

Create services with a few settings and group them into projects. Use the advanced options when you need more control.

01

Applications

Choose a container image, add a domain, and deploy. Upvale sets up HTTPS and keeps your logs and deployment history.

  • Deploy from a container image
  • Domains & automatic HTTPS
  • Logs, terminals & revisions
02

Databases

Create a PostgreSQL, Redis, or MongoDB database. Set up backups and copy the connection details into your app.

  • Scheduled database backups
  • PostgreSQL high availability
  • PostgreSQL read replicas
03

Scheduled jobs

Run imports, reports, or cleanup tasks on a schedule. Check the output or start a run from the dashboard.

  • Cron schedules & timezones
  • Run on demand
  • Run history & logs

02 / POSTGRESQL HIGH AVAILABILITY

PostgreSQL with
automatic failover.

Connect at least three servers, choose managed PostgreSQL, and select your primary and standby nodes. Upvale configures replication and automatic failover. Add read replicas from the same screen.

Automatic failover

If the primary fails, an eligible standby can take over. Your application reconnects through the same writer endpoint.

Read replicas

Let selected standby nodes serve reads as well. Upvale gives your app a reader connection and balances new connections across the healthy replicas you choose.

Share reads when needed

Keep reads on the primary until it gets busy, then share the load with replicas. For example: above 80% server CPU for a minute. You choose the threshold and duration.

Connection routingExample · primary excluded from reads
Writer endpointWrites & current data
Primarynode-01
Data replicates to the standbys
Reader endpointBalanced connections
Standbynode-02
Standbynode-03

Replicas must pass health and replication-lag checks before receiving new read connections.

Two connections in your app

Send read traffic to the separate reader endpoint. Keep writes, and reads that need to see the latest write, on the writer endpoint. Replica data can lag behind the primary.

03 / DOCKER COMPOSE

Use your
Compose file.

Prefer to define your services in a file? Import your Compose configuration and manage its services from the dashboard.

  1. 01

    Import your file

    Import image-based services into your project. Choose which compatible database services Upvale should manage.

  2. 02

    Review the changes

    See what will be created, updated, or removed before you apply the file. Unsupported options are flagged here.

  3. 03

    Manage your services

    Read logs and inspect deployments for each service. Edit the Compose file when you want to change their configuration.

compose.yamlEXAMPLE
# Web app, API, and PostgreSQL
services:
  web:
    image: ghcr.io/fieldnotes/web:1.8.2
    ports: ["3000:3000"]
    depends_on: [api]

  api:
    image: ghcr.io/fieldnotes/api:1.8.2
    depends_on: [postgres]

  postgres:
    image: postgres:17
    environment:
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
    volumes: ["db-data:/var/lib/postgresql/data"]

volumes:
  db-data:
Supported servicesPreview → Apply
web api postgres

Imported services appear alongside the rest of your project.

04 / MAINTENANCE

Updates, backups
and monitoring.

Update servers, schedule backups, and check for problems from the dashboard.

Server updates

Choose when to update. Upvale applies the updates and checks that the server comes back online.

Back up and restore

Schedule database backups to your S3 storage. Restore into a new database and verify your data before switching over.

See what changed

Compare configuration between revisions and follow the deployment steps to see where a change went wrong.

Investigate a problem

Check server health, read the service logs, and review alerts from the same dashboard.

Permissions and audit logs

Control what teammates can access. Solo and Team include audit logs to track deployments and other changes.

YOUR INFRASTRUCTUREILLUSTRATED
Your dashboard
Production clusterYOUR SERVERS
node-01 Connected
node-02 Connected
node-03 Connected
Applications Databases Jobs

Application traffic stays on your infrastructure.

05 / PRICING

Choose your plan.

Two months free with yearly billing.

Free

For trying Upvale.

$0/month

Free. No subscription payment.

Start free
  • 1 cluster
  • 3 nodes in total
  • 1 user
  • Apps, databases & jobs
  • PostgreSQL HA & read replicas
  • Managed Compose

Solo

For individual developers.

$5/month

Billed monthly.

Choose Solo
  • 2 clusters
  • 10 nodes in total
  • 1 user
  • Apps, databases & jobs
  • PostgreSQL HA & read replicas
  • Managed Compose
  • Audit logs

Team

For teams working together.

$19/month

Billed monthly.

Choose Team
  • 10 clusters
  • 50 nodes in total
  • 5 users
  • Apps, databases & jobs
  • PostgreSQL HA & read replicas
  • Managed Compose
  • Audit logs

Enterprise

For larger teams and custom needs.

Custom

Contact us for pricing.

Contact us
  • Custom cluster limits
  • Custom node limits
  • Custom user limits
  • Everything in Team
  • Discuss your support needs

Prices are in USD, per organization. Server and backup storage bills are paid separately to your providers. Node limits cover all clusters in the organization.

FAQ

Common questions.

How do I get started?

Connect a Linux server using the setup command, then deploy a container image from the dashboard. Apps, databases, and scheduled jobs each have their own form. Compose is optional.

Does the price include my servers?

No. You pay your server and backup storage providers separately. Upvale’s subscription covers the dashboard and management of your servers, with no extra fee per app, database, or job.

Where do my applications actually run?

On the Linux servers you connect to Upvale. You choose the provider and server sizes. Upvale hosts the dashboard and manages deployments.

Can I keep my existing build pipeline?

Yes. Keep building images in your current CI pipeline and pushing them to your registry. A deployment webhook can tell Upvale to deploy the new image after a successful build.

Can I bring a Docker Compose file?

Yes. Enable managed Compose in your project, import a file, and review the changes before deploying. Services need prebuilt container images. Upvale flags unsupported settings before you apply the file.

Are node updates automatic?

You start updates from the dashboard. Upvale applies them and checks that the server comes back online. Agent updates run one server at a time. System package updates require a supported APT-based Linux system. Updates do not run on a schedule.

What do I need for a highly available database?

Connect at least three eligible servers to your cluster, then create a managed PostgreSQL HA database and choose its primary and standby nodes. Upvale configures replication and automatic failover. Optional read replicas use a separate reader connection in your app.

How do database backups and restores work?

Choose an S3-compatible storage destination, a schedule, and how long to keep backups. A restore creates a new database so you can check the recovered data before pointing your application at it.

What if the control plane goes offline?

Your running workloads stay on your servers, and application traffic does not pass through the control plane. You will need the control plane back online to deploy changes or manage resources.

UPVALE

Try Upvale for free.

Connect a server and deploy your first app.

Start free