Starter
One production app.
Billed monthly
Join early access- 1 app, 1 GB RAM
- Automatic HTTPS and custom domain
- Deploy from GitHub
- Daily database backups

Papel Cloud, in early access
Papel Cloud builds and runs web apps and APIs on AWS, with a preview environment for every pull request, managed PostgreSQL, backups and logs. You keep the code; we run the infrastructure.
The jobs Papel Cloud is designed to do, and the teams it suits best.
Apps built under a Growth or Scale development plan run on Papel Cloud by default, with deploys, backups and monitoring set up from the first release.
Get containers, a managed database and HTTPS on AWS without writing infrastructure code or managing servers.
Product managers, designers and clients test every pull request on its own URL before it merges.
Line-of-business apps that need a database, backups and logs, without a dedicated operations team.
Connect a repository and branch. Every push builds a container image and rolls it out with health checks.
Each pull request gets its own URL with a copy of the app, posted as a comment on the PR and removed when it closes.
Every deploy is kept as a release. Roll back to any previous one from the dashboard or the CLI.
Provisioned on Amazon RDS with connection strings injected as environment variables.
Automatic daily snapshots on every plan, with point-in-time restore on Pro and above.
Encrypted environment variables per environment, with an audit trail of who changed what.
Add your domain, follow the DNS instructions, and traffic routes to your app once records verify.
TLS certificates are issued and renewed for every domain. HTTP redirects to HTTPS by default.
Apps and databases talk over a private network. Business plans can peer with your own VPC.
Build and runtime logs in one searchable view, retained for 7 days on Starter and 30 days on Pro.
CPU, memory, response time and error rate per app, so you can see when it's time to resize.
Change instance size or count from the dashboard without redeploying your code.
Install the Papel Cloud GitHub app on the repositories you choose and pick the production branch.
We detect Node.js, Python, Go or a Dockerfile. Set the start command, environment variables and whether you need a database.
Each push to the branch builds an image, runs your release command such as migrations, and replaces instances once health checks pass.
Pull requests get a preview URL. Reviewers test the change there before it merges.
Point DNS at Papel Cloud, and HTTPS is issued automatically. Logs, metrics and backups run from the first deploy.
What happens between a push to GitHub and traffic reaching your app. Each stage runs on AWS.
Step 1: Your repository
GitHub
Push to the production branch, or open a pull request for a preview.
Your code and Dockerfile
Node.js, Python and Go detected automatically.
Step 2: Build
Container image
Built from your code and stored as a release.
Release command
Runs migrations or other steps before traffic switches.
Step 3: Papel Cloud on AWS
App instances
Containers behind a load balancer, replaced only after health checks pass.
Managed PostgreSQL
Amazon RDS on a private network, with backups.
Domains and HTTPS
Certificates issued and renewed automatically.
Step 4: Operate
Logs and metrics
Build and runtime logs, CPU, memory and response times.
Rollback
Any previous release, from the dashboard or CLI.
Alerts
Slack notifications and Papel Monitor checks.
Apps and databases talk over a private network; databases aren't exposed to the internet.
Business plans run in a dedicated AWS account in the region you choose, and can peer with your VPC.
Your app is a standard container and your database is PostgreSQL, so you can move them elsewhere.
What the people who own Papel Cloud in your company can configure, review and restrict.
| Service | What it does |
|---|---|
| GitHub | Deploys, PR previews and status checks |
| Amazon Web Services | Compute, RDS PostgreSQL and S3 |
| Docker | Bring your own Dockerfile |
| Node.js, Python, Go | Detected automatically |
| Papel Monitor | Uptime and error tracking for each app |
| Slack | Deploy and failure notifications |
| Any DNS provider | Custom domains via CNAME or A records |
Apps run in AWS data centers in the United States by default. Business plans can choose a region and get a dedicated AWS account.
Databases, backups and secrets are encrypted at rest. All traffic to your apps is served over TLS.
Production access for our staff requires SSO with multi-factor authentication and is logged.
We read your repository only to build it. Disconnect at any time and export your database with standard PostgreSQL tools.
More detail on our security practices and Privacy Policy.
Prices in US dollars, billed monthly. You aren't charged during early access until your workspace is live, and you can cancel at the end of any billing period.
One production app.
Billed monthly
Join early accessSeveral apps and environments.
Billed monthly
Join early accessDedicated AWS account.
Quoted to your scope, billed monthly or annually
Talk to salesWhat each plan includes, side by side. Figures match our pricing page; if anything here and your order form differ, the order form applies.
| Limit | Starter$12 per month | Pro$49 per month | BusinessCustom quote |
|---|---|---|---|
| Apps | 1 | Up to 3 | Custom |
| Memory per app | 1 GB | 2 GB each | Custom |
| Preview environments | Not included | One per pull request | One per pull request |
| Database | Database with daily backups | Managed PostgreSQL, daily backups | Managed PostgreSQL in your dedicated account |
| Point-in-time restore | Not included | 7 days | Custom |
| Log retention | 7 days | 30 days | Custom |
| AWS region | US East (N. Virginia) | US East (N. Virginia) | Your choice |
| AWS account | Shared platform | Shared platform | Dedicated per client |
| VPC peering | Not included | Not included | Included |
| Uptime commitment | Not covered | 99.9% under our SLA | Custom SLA |
See also our Acceptable Use Policy and Service Level Agreement.
Work we plan or are exploring, in no particular order. We don't promise dates: priorities follow what early-access customers ask for, and plans can change.
Defining and monitoring cron-style jobs alongside your app, with run history and failure alerts.
Adding and removing instances automatically based on CPU or request load, within limits you set.
Choosing a region other than US East on Starter and Pro plans.
A managed cache and queue alongside PostgreSQL, on the same private network.
Deploys and preview environments from GitLab repositories as well as GitHub.
By default, US East (N. Virginia). Business plans run in an isolated AWS account and can choose another region.
Anything that runs in a container. We auto-detect Node.js (including Next.js), Python and Go, and you can supply your own Dockerfile for anything else.
Yes. Your code lives in your repository, apps are standard containers and the database is PostgreSQL, so you can export and run them elsewhere.
No. Papel Cloud is a managed platform. You control the app, its configuration and its database; we manage the servers underneath.
Yes. Growth and Scale development plans include hosting for the apps we build for you.
New instances must pass health checks before they receive traffic, and the release command runs before the switch. If something goes wrong, roll back to the previous release in one step.
Business plans run in a dedicated AWS account per client. If you'd rather manage everything in an account you already own, our Cloud and DevOps service sets that up for you.
No. Papel Cloud plans are paid, but during early access you aren't charged until your workspace is live.

Tell us about your app and we'll set up your workspace with you. Billing starts when it's live.