Overview - Hoista

Hoista works with the accounts you already have at these providers. Each page covers how to connect the provider and what Hoista can do there.

Hosting providers

Cloudflare

Workers, Pages, D1, KV, R2 and DNS zones

Vercel

Frontends and serverless functions

Railway

Services, workers and databases in Railway projects

Fly.io

Apps on Machines that sleep when idle

Render

Web services, workers, cron jobs, Postgres and Key Value

Database providers

Neon

Serverless Postgres

Supabase

Postgres with auth, storage and Edge Functions

GPU providers

Runpod

Pods, Serverless endpoints and network volumes

Modal

Serverless GPU apps and their volumes

Email providers

Resend

Sending domains for your apps’ email

Git providers

GitHub

The repositories your projects are built from

Compare

What Hoista does with each provider:

Provider	What Hoista finds	Create and deploy	Logs	Metrics	Variables	Billing
Cloudflare	Workers, Pages projects, D1 databases, KV namespaces, R2 buckets, zones	Workers from a folder, rollback, D1 databases, R2 buckets	Yes	Yes	Variables and secrets	Bill
Vercel	Projects	Projects from a repository	Yes	Yes	Yes	Bill
Railway	Services and databases	Services from a folder, repository or image, redeploy and rollback, databases, buckets	Yes	Yes	Yes	Bill
Fly.io	Apps and their Machines	Apps from a folder or image, rollback, pause and resume	Yes	Yes	Variables and secrets	No
Render	Web services, background workers, cron jobs, Postgres databases and Key Value stores	Web services and Postgres databases	No	Yes	Yes	No
Neon	Projects (Postgres)	Postgres databases	No	Paid plans	No	Plan usage
Supabase	Projects, with their Postgres database, Edge Functions and Storage buckets	New projects	Yes	Yes	Yes	No
Runpod	Pods, Serverless endpoints, network volumes	Pods and endpoints from a folder or image	Yes	Yes	No	Bill
Modal	Apps and volumes in every environment	Apps from a folder	Yes	Yes	No	Bill
Resend	Sending domains	Sending domains	Yes	Yes	No	Plan usage
GitHub	Repositories	Nothing runs on GitHub	No	No	No	No

With every provider except GitHub you can also:

Open the tab named after the provider (such as Railway) to read a resource’s settings and run the provider’s own operations. A project on several providers shows one Providers tab instead.
Delete a resource at the provider after you confirm it by name.

Some features work with only a few providers:

Custom domains through hoist domains: Cloudflare and Fly.io.
Daily usage through hoist usage: Cloudflare and Railway.
Running your remote: Railway and Fly.io.
Signing in through the browser instead of pasting a token: Railway, and Cloudflare and Vercel when your build of Hoista includes their sign-in app.

Bill is the amount the provider has billed so far this period. Plan usage is how much of the plan you have used, for providers that share usage but no money figure. Hoista never estimates cost. See Billing.

Check your installed version

hoist providers

This lists each provider your version supports and the name to use with hoist accounts add. What you can do there also depends on the token’s permissions and your plan with that provider. Agents can call get_my_access to see what their connection may do, then list_provider_operations and describe_provider_operation for a provider’s own operations. See MCP.

Connect hosting accounts

Connect, check and rotate accounts.

Bring in a project

Add what an account already runs.

Billing

What each provider has billed.

​Hosting providers