Welcome to Upferry

What Upferry does

Upferry runs web applications, APIs, background workers, scheduled jobs, and databases from one panel. Deploy from a GitHub repository, a container image, or a local folder using the CLI. Applications can use generated HTTPS addresses, custom domains, persistent volumes, and private service connections.

The current hosted instance is a private preview for approved GitHub accounts. An invitation or operator approval is required. These docs describe shipped functionality, not a promise of public signup, paid plans, multiple regions, or high availability.

Projects, services, and environments

A project groups related services. A service describes one application, worker, or database. An environment gives that project its own variables, deployments, generated domains, and volumes. Production is created with the project; staging and pull request previews are separate environments.

A project itself is not a website. A web service gets its own generated address when public networking is configured. Each environment has a separate generated hostname. Repeated deployments of that service keep the configured hostname.

Choose your next step

• Deploy your first service from GitHub.
• Move from Railway with a deliberate data and DNS cutover.
• Use the CLI to deploy a local folder.
• Configure backups before you depend on persistent data.

For a Shopify starting point, see the Shopify Python launch guide. It provides starter application code; connecting a Shopify store still requires the app setup and permissions described there.

The panel and workloads currently share one server. Resource limits and network permissions improve operational control, but do not provide a complete boundary for arbitrary untrusted builds. See integrations and limits.