10,000
credits
Package price$10
Credit-based pricing
Buy credits. Run live apps. Pay for actual runtime.
ulv.sh uses one wallet for app, database, and service deployments. Live workloads consume credits per minute by instance size; pending and failed deploys do not.
Credit wallet
Shared by apps, databases, and services
active
Starting bonus
200,000
Credit value
$0.001
Low warning
5,000
Live deployment meter
PENDINGnot billed
LIVEbilled per minute
REPLACEDbilling stopped
FAILEDnot billed
Credit packages
Top up once. Spend across every workload.
Each package maps directly to USD at $0.001per credit. Admin grants and usage deductions use the same transaction history as purchases.
20,000
credits
Package price$20
50,000
credits
Package price$50
100,000
credits
Package price$100
200,000
credits
Package price$200
500,000
credits
Package price$500
Instance pricing
Pick the runtime size for each deployment.
Instance type is snapshotted onto each deployment. Billing uses the live deployment duration multiplied by the instance per-minute rate.
Size
vCPU
Memory
Credits / min
Approx / 30d
xs
1
2 GB
0.925
39,960 cr
sm
2
4 GB
1.85
79,920 cr
md
4
8 GB
3.70
159,840 cr
lg
8
16 GB
7.40
319,680 cr
xl
16
32 GB
14.80
639,360 cr
How billing works
Predictable rules for unpredictable traffic.
Usage is calculated from live deployment records. The platform keeps pending usage visible, then settles due users at the first of the month in UTC.
Buy credits
Credits are prepaid through Stripe and held on your account balance.
Run live deployments
Billing starts only when a deployment becomes LIVE and stops when it is replaced, stopped, or suspended.
Settle monthly
Usage accrues as pending credits and is deducted once per month from the same wallet.
Example daily usage
App + database + worker
web-api
sm instance, 24h live
2,664 cr
postgres
xs instance, 24h live
1,332 cr
worker
xs instance, 6h live
333 cr
Total4,329 cr
Out-of-credit guardrails
When effective balance reaches zero, active apps are suspended and live workloads stop accruing new runtime.
Suspended apps become read-only. Logs stay readable, domain links stay visible, and recovery happens through a redeploy after credits are positive again.
Adding credits alone does not silently restart infrastructure; the user stays in control of the recovery deploy.
Common questions
Pricing without fake tiers.
What is one credit worth?
One credit equals $0.001 USD. A 10,000 credit package costs $10.
When does billing start?
Billing starts when a deployment transitions to LIVE. Pending and failed deployments are not billed.
What happens if my balance reaches zero?
Active applications are suspended, live workloads are stopped, and the app becomes read-only. Add credits, then redeploy to recover.
Can I use the same credits for apps and databases?
Yes. GitHub apps, service apps, and database apps all draw from the same credit wallet when their deployments are live.