Polyer

Application deployment and hosting

Deploy your code. Keep your services running.

For developers deploying websites, APIs, background jobs and databases from GitHub, Docker images or templates. Connect your services and manage releases, logs and persistent storage in one project.

  • Billed by the minute for the CPU, memory, egress and disk you actually use.
  • $1 of Free allowance every 30 days, for as long as you like. No card required.
  • Set a spend limit and get alerts before you reach it.
Create your account Explore templates

Create an account, choose your source and review the configuration. Resources are created when you submit the deployment.

launch-padProduction
Architecture
Web service

frontend

your-team / website

Public endpoint
Web service

api

GitHub / main

Private network
Database5 GB

PostgreSQL

postgres.internal

Persistent volume
HTTPSQL

Illustrative configuration. No live project data.

Choose how to deploy your application.

GitHub repository

Bring a repository you can access, then choose a branch, build settings and runtime variables.

Explore GitHub deployment

Docker image

Bring an image reference. Review its start command, listening port, variables and persistent data paths.

Explore Docker hosting

Deployment template

Compare ready-made service configurations for n8n, WordPress and databases. Review inputs and compatibility before deploying.

Explore open-source hosting

Deployment is the start.
See what happens next.

Review connections, releases and resource settings in one project, with logs to help investigate problems.

See every release

Follow each deployment from build to startup, with records and logs together. Inspect the relevant service's output when something goes wrong.

  • Review pending configuration changes before submitting a deployment.
  • Use build and runtime logs to investigate startup and connection errors.
apiProduction
Deployments
main · 7a3d2f1

Source revision

  1. Build completed01
  2. Container started02
  3. Application output03
Build outputRuntime logs
01[build] npm run build
02[build] compilation finished
03[service] listening on :3000
04[database] connection ready

Control configuration and resources

Manage variables, domains, persistent storage and resources together. Understand operating costs through usage and regional prices.

  • Connect services over the private network and reference their variables, such as DATABASE_URL, instead of copying values.
  • Configure shared and service-specific variables, then review pending changes.
  • Attach volumes for persistent data and review resource usage alongside billing.
apiProduction
Configuration

Environment variables

2
DATABASE_URL${{postgres.DATABASE_URL}}
PORT3000

Resources

CPU0.5 vCPU
Memory512 MB
Data volume/data
5 GB
Pending changesPORT → 3000

Useful apps. Start with a template.

Browse the marketplace

n8n

Connect APIs and webhooks to build automated workflows.

WordPress

Deploy your website and database, and manage content and uploads.

PostgreSQL

Use relational data and private connections. Review storage settings.

Redis

Cache data, run queues and share state between services.

Uptime Kuma

Monitor websites and APIs, and get notified when they go down.

MySQL

A relational database for applications that expect MySQL.

Usage-based pricing. Estimate before you deploy.

Example: a small API

CPU 0.5 vCPU
$4.00
Memory 512 MB
$2.00
Volume 1 GB
$0.06
30 days at its configured maximum
$6.06

Base-region resource estimate, excluding outbound traffic and plan credits. Actual usage and regional prices determine your bill.

Hobby ($3/month) and Pro ($10/month) plans include their fee as usage credit.

Review pricing

Before you start

What can I deploy?

Deploy websites, APIs, background jobs and databases from GitHub, Docker images or templates. Choose a supported service configuration and review regional capacity.

What should I prepare before deploying?

Choose a repository, Docker image or template. Have the build or start command, required secrets, service connections and persistent data paths ready. Web services need a listening port; background workers can run without a public endpoint. Review the selected region and estimated cost before submitting.

What do I still manage myself?

Polyer provides deployment controls, service configuration, logs and resource usage. You remain responsible for application setup, secrets, software updates and testing your backup and recovery process. A template provides configuration; it does not mean every application workflow has been tested for your needs.

How is application data stored?

Attach a persistent volume for local data that must survive service restarts. For a website with a database, plan recovery for both uploaded files and database records. A volume is not a backup: review available backup options and test restoration before relying on them.

How are costs calculated?

CPU, memory, storage and network are billed by usage. Regional prices and plan credits affect the bill. Third-party APIs, application licenses and other external services are separate.

A place to run your next project.

Create your account Explore templates

Create an account, choose your source and review the configuration. Resources are created when you submit the deployment.