Skip to content

Community capacity

You choose where each app and each HivePod runs:

DockHive-managed (default) Community
Runs on DockHive’s own infrastructure Machines owned by independent, vetted operators
Price Published prices 30% cheaper
Good for Production and anything confidential Cost-sensitive work that isn’t confidential
Available for Every app and pod Apps and Linux pods, in regions that have community capacity

DockHive-managed is the default. You only run on community capacity when you choose it for an app or a pod and confirm the notice below.

Read this before you choose community capacity. It is the notice the console and the API ask you to accept.

Community capacity: who can access your app

Community capacity runs on machines owned by independent, vetted operators. The operator of the machine your app runs on can access your app’s code, its settings (including environment variables and secrets), the files it stores and the traffic it receives, including your domain name and your visitors’ requests. Use DockHive-managed capacity for anything confidential.

I understand that the operator of the machine can access my app’s code, settings, stored files and traffic.

If the app has environment variables, you confirm a second notice too:

This app has environment variables. On community capacity the machine’s operator can read them, including passwords, API keys and database connection strings. Keep apps with secrets on DockHive-managed capacity, or confirm below.

I accept that the operator can read these settings.

Community capacity: who can access your pod

Community capacity runs on machines owned by independent, vetted operators. The operator of the machine your pod runs on can access your pod’s code, its settings (including environment variables and secrets), the files it stores and the traffic it receives, including your domain name and your visitors’ requests. Use DockHive-managed capacity for anything confidential.

I understand that the operator of the machine can access my pod’s code, settings, stored files and traffic.

If the pod has environment variables, you confirm a second notice too:

This pod has environment variables. On community capacity the machine’s operator can read them, including passwords, API keys and database connection strings. Keep pods with secrets on DockHive-managed capacity, or confirm below.

I accept that the operator can read these settings.

DockHive records each confirmation: who accepted it, when, and which version of the notice.

Community capacity is billed at 70% of the DockHive-managed price. Compute is billed by the hour while the app or pod runs, and memory is included.

DockHive-managed Community
Compute $2 per vCPU-month $1.40 per vCPU-month

HivePods, always on, per month:

Size vCPU DockHive-managed Community
Nano 0.5 $1 $0.70
Micro 1 $2 $1.40
Small 2 $4 $2.80
Medium 4 $8 $5.60

App sizes, per month while running:

Size vCPU DockHive-managed Community
512 MB 0.5 Included Included
1 GB 1 $2 $1.40
2 GB 2 $4 $2.80
4 GB 4 $8 $5.60

Your plan’s included vCPU-hours come off first, the same as on DockHive-managed capacity. Usage beyond them is shown and billed at the Community price. See Usage and overage.

Choose DockHive-managed for production, for anything confidential (customer data, payments, private code) and for apps or pods whose settings hold passwords, API keys or database connection strings. It comes with full DockHive support.

Choose Community for cost-sensitive work that isn’t confidential: side projects, previews and demos, open-source apps, test environments and batch jobs.

  • A region that has community capacity. The console only offers Community where it is available.
  • A verified card on your account (see Create an account).
  • An account in good standing: a credit balance that isn’t below zero, and no suspension.
  • HivePods: Linux environments only. App Marketplace pods and full-machine pods (VMs) always run on DockHive-managed capacity.
  • A new app: in New app, choose Where it runs: Community, then read and confirm the notice.
  • A new pod: in New environment, pick a Linux OS and choose Where it runs: Community, then read and confirm the notice.
  • An existing app: open the app, go to Builds & Settings > Where it runs, choose Community and confirm. The change applies on the app’s next deploy. Moving it back to DockHive-managed works the same way.

If the app or pod has environment variables, the console asks for the second confirmation as well.

With the hivepod CLI (version 0.6.0 or later), add --capacity community. The CLI shows the notice and asks you to confirm it:

Terminal window
hivepod create web1 --os ubuntu-24.04 --size micro --capacity community
hivepod deploy --capacity community --repo
hivepod app capacity my-app community # an existing app; applies on its next deploy

In scripts and CI, where nothing can be asked, accept the notice with flags after reading it on this page: --accept-community-notice, plus --accept-community-secrets when the app or pod has environment variables. The CLI always sends the version of the notice the server shows, so a changed notice is never accepted without being shown.

Send capacity_class: "community" with the version of the notice you accepted in community_ack. When the app or pod has environment variables, also send community_secrets_ack with the same version. The current notice version is 2026-11-15; read it from the API rather than hard-coding it.

The capacity classes, whether you can choose Community right now, and the current notice:

Terminal window
curl https://api.dockhive.io/api/v1/apps/capacity-classes -H "Authorization: Bearer $DOCKHIVE_API_KEY"
curl https://api.dockhive.io/api/v1/hivepods/capacity-classes/ -H "Authorization: Bearer $DOCKHIVE_API_KEY"

Create a pod on community capacity:

Terminal window
curl -X POST https://api.dockhive.io/api/v1/hivepods/ \
-H "Authorization: Bearer $DOCKHIVE_API_KEY" -H "Content-Type: application/json" -H "X-Region: eu" \
-d '{
"name": "web1",
"os_image": "ubuntu-24.04",
"resource_tier": "micro",
"environment_variables": {"APP_ENV": "dev"},
"capacity_class": "community",
"community_ack": "2026-11-15",
"community_secrets_ack": "2026-11-15"
}'

Move an existing app (applies on its next deploy):

Terminal window
curl -X PATCH https://api.dockhive.io/api/v1/apps/projects/<app-id> \
-H "Authorization: Bearer $DOCKHIVE_API_KEY" -H "Content-Type: application/json" \
-d '{"capacity_class": "community", "community_ack": "2026-11-15", "community_secrets_ack": "2026-11-15"}'

The same fields work when you create an app (POST /api/v1/apps/projects) or deploy one from a repository (POST /api/v1/apps/deploy). The app sizes list (GET /api/v1/apps/app-sizes) includes community_price_monthly_cents and community_price_label for each size.

Without the confirmations the API answers 409 and includes a disclosure object with the current notice (version, title, text, ack_label, secrets_text, secrets_ack_label):

Status Code Meaning
409 community_ack_required Accept the community capacity notice: send community_ack with the current version. Also returned when the notice has changed since you accepted it.
409 community_secrets_blocked The app or pod has environment variables: send community_secrets_ack too, or keep it on DockHive-managed capacity.
402 card_required Verify a card in Billing first.
402 credit_required Your credit balance is below zero. Top up first.
503 capacity_unavailable Community capacity can’t be chosen right now. Try again later or use DockHive-managed.
  • Creating or moving an app or pod with environment variables on community capacity needs the second confirmation.
  • Changing a community pod’s environment variables asks again: send community_secrets_ack with the change (PATCH /api/v1/hivepods/<id>/), or confirm in the console. hivepod env asks for you, or takes --accept-community-secrets.
  • Linked databases reach your app as environment variables, so they count too.

If DockHive updates the notice, running apps and pods keep running as they are. Before the next deploy on community capacity, the owner confirms the new version (in the console, with the CLI, or by sending the new version in community_ack). Until then, deploys answer community_ack_required.

Operators can leave or take a machine out of service. When that happens, a community app or pod is moved to another machine automatically and keeps the Community price. Keep what matters in your app’s repository and your pod’s data and projects folders, and use backups for pods.