XPod App — ready-made apps we keep up to date

How it works

Four steps, without maintaining versions yourself

Pick from the catalog
Apps we maintain ourselves, not a long list nobody has ever tested.
Pick a size
Each app has a few plans. What differs is the resources, not the features.
Fill in only what's needed
Admin credentials are generated for you. We only ask what only you know.
Use it
The subdomain and HTTPS are live as soon as the deploy finishes. Your own domain can follow.

Catalog

This list is read straight from the catalog, with current prices.

synced live from the XPod catalog

When not to use XPod App

If your need is one of these, don't force it into App. Use the XPod product built for it.

Your app isn't in the catalog
If you already have your own image, there's no need to wait for us to add it.
To XPod Run →
You only need to serve static files
A built site doesn't need anything that stays up, and shouldn't be billed while quiet.
To XPod Sites →
You only need to run once in a while
A script that runs every night isn't worth paying for 24 hours a day.
To XPod Jobs →

Seven products, one platform

The difference is when your code runs: from always on, to not running at all until it is needed.

Product	What you bring	When it runs	How it is billed
XPod Appyou are here	An app from the catalog	Always	Monthly
XPod Run	Your own container image	Always	Monthly, per active minute
XPod Base	A PostgreSQL database	Always	Monthly
XPod Sites	Static files	Never	Plan + bandwidth
XPod Jobs	Code in a container	On a schedule	Per second of execution
XPod Queue	Code or a container	When messages arrive	Per processed message
XPod Functions	One function (handler)	When called	Per call + GB-second