Plans
Four plans are available. Each plan carries a monthly base fee and an equal amount of usage credit included at no extra charge. When your metered usage stays inside that credit, you pay the base fee and nothing more. When usage exceeds the included credit, you pay for the overage on top.
Free - No base fee. A small usage credit is included. Good for personal experiments and one-off deploys.Hobby - A modest base fee with a matching usage credit. Covers a small production app running around the clock.Pro - A mid-tier base fee and matching credit. Intended for teams shipping customer-facing products.Team - The highest base fee and the largest included credit. Covers larger teams with multiple concurrent services and higher sustained throughput.
See current rates on the pricing section of the homepage.
Metered units
Usage is measured in four dimensions. Every running service accumulates a cost in each dimension; the sum across all services in a team is your total metered usage for the month.
memory - Billed in GB-hours. One service allocated 512 MB running for 24 hours consumes 12 GB-hours.vCPU - Billed in vCPU-hours. Charged only for the CPU allocated to your service, not for peak usage within that allocation.egress - Billed per GB of outbound data leaving the Fieldwick network. Traffic between services inside the same region is not charged.storage - Billed in GB-months. Covers persistent volumes attached to services and managed database storage.
The bill formula is:
bill = max(plan_base_fee, total_metered_usage)
If your metered usage falls below the plan base fee, you pay the base fee. If it exceeds the base fee, you pay the actual usage. There is no scenario where you pay both.
Spend caps
Every team can set a monthly USD spend cap. The cap is a hard ceiling: Fieldwick checks projected spend before each deploy and refuses the deploy if accepting it would push the team over the cap.
When a running team approaches or hits its cap, two actions are available:
throttle - CPU and network throughput are reduced to a minimal level. Services stay alive and reachable but run slowly until the cap resets at the start of the next billing cycle.pause - All allocations for the team are stopped. Services become unavailable until the cap resets or the operator raises the cap manually. No compute or egress accrues while paused.
You set the cap action in your team settings. The default action on a new team is throttle. To never have services go down automatically, keep the default. To guarantee zero overspend at the cost of availability, switch to pause.
Checkout and payment portal
Fieldwick uses Stripe for all payment processing. When you upgrade a plan or add a payment method, you are redirected to a Stripe-hosted checkout page. Your card details never touch Fieldwick servers.
To update your payment method, download invoices, or change your billing email, open the Stripe customer portal from your team settings page. Changes take effect immediately; the next invoice reflects the updated information.
Checking your bill from the CLI
The fieldwick billing commands let you inspect your current bill and usage without opening the dashboard. Both commands accept a team ID as the first positional argument.
Show the current billing status for a team - plan, cap, amount used so far this cycle, and projected end-of-month total:
fieldwick billing show <team-id>
Show a breakdown of metered usage by dimension (memory, vCPU, egress, storage) for a specific month. The --month flag accepts an ISO year-month string:
fieldwick billing usage <team-id> --month 2026-06
Both commands output plain text by default. Append --json to get machine-readable output suitable for piping into monitoring scripts or dashboards.
Regions and egress costs
Fieldwick runs services in two regions: us-east-1 and eu-central-1. Traffic between two services in the same region is free. Traffic leaving the Fieldwick network to the public internet or to services in a different region counts as billable egress.
Deploying a service to the region closest to your users reduces egress costs because more traffic stays inside the region boundary. See Regions for how to set the region on a service and how egress is counted when services span regions.