Pricing

w7s.cloud is free to start. You do not need a W7S account, a credit card, or a separate cloud setup to deploy through the hosted service.

The hosted service is still intentionally simple: small apps can deploy, test, demo, and share before billing matters. When an app starts getting meaningful traffic, the model should be usage-based instead of a mandatory subscription just to keep the app online.

The serverless DB is part of that model. If an app uses the W7S serverless database, database reads, writes, and stored data are included in the W7S usage estimate instead of requiring a separate database bill to understand the real cost shape. External Postgres is still possible when an app needs it.

Interactive estimate

Pick a startup stage.

Each stage sets the sliders to a common startup shape. The first stage is the top of the included free tier, so it prices at zero.

Estimated monthly cost$0.00Billable overage after the included free-tier baseline, W7S overhead, and 50% gross margin.

Top of the included free-tier baseline. This stage should estimate $0.00.

Monthly visitors3K

Runtime requests180K

Backend requests15K

CPU time93.8K ms

Visitors per day100Human visitors reaching the app each day.Page views per visitor5Used to estimate HTML requests and asset delivery.Static assets per page10Scripts, CSS files, images, fonts, and generated files.Backend requests per page1API calls or native backend routes triggered by each page view.Average backend CPU5 msW7S caps backend CPU, but heavier handlers still cost more.Static cache hit rate50%Higher cache hits reduce origin reads for immutable assets.

More infrastructure sliders

Key-value reads per visitor1Sessions, feature flags, config, or cache lookups.Key-value writes per 100 visitors1Light session or state writes.SQL rows read per visitor10Rows scanned by queries, not just rows returned.SQL rows written per 100 visitors1Inserts, updates, deletes, and index writes.FS reads per 100 visitors0App FS reads outside the static asset cache.FS writes per 100 visitors0Uploads or generated files written to FS.Queue messages per 100 visitors0Each delivered message is roughly one write, one read, and one delete.Stateful object calls per 100 visitors0Stateful coordination, counters, rooms, locks, or sessions.Stateful object active seconds per day0 secOnly active non-hibernated wall-clock time is estimated here.Log events per visitor0Console logs and exceptions retained by W7S.Static asset storage1 GBBuilt frontend files and immutable deploy assets.App FS storage0 GBUser uploads or generated files stored in FS.Key-value storage1 GBKey-value data stored by the app.SQL storage1 GBSQLite-backed relational data.Stateful object storage0 GBSQLite-backed stateful object data.Deployed runtimes1Usually one script per deployed backend/environment.

Monthly breakdown

Area	Billable usage	Rate	Estimate
Runtime requests	0	$0.30 / 1M	$0.00
Runtime CPU	0 ms	$0.02 / 1M ms	$0.00
Deployed runtimes	0	$0.02 / runtime	$0.00
Asset and FS storage	0 GB	$0.015 / GB	$0.00
FS write operations	0	$4.50 / 1M	$0.00
FS read operations	0	$0.36 / 1M	$0.00
Key-value reads	0	$0.50 / 1M	$0.00
Key-value writes	0	$5.00 / 1M	$0.00
Key-value storage	0 GB	$0.50 / GB	$0.00
SQL rows read	0	$0.001 / 1M	$0.00
SQL rows written	0	$1.00 / 1M	$0.00
SQL storage	0 GB	$0.75 / GB	$0.00
Queue operations	0	$0.40 / 1M	$0.00
Stateful object requests	0	$0.15 / 1M	$0.00
Stateful object duration	0 GB-s	$12.50 / 1M GB-s	$0.00
Stateful object storage	0 GB	$0.20 / GB	$0.00
App logs	0	$0.60 / 1M	$0.00
W7S routing executions	0	$0.30 / 1M	$0.00
W7S routing CPU	0 ms	$0.02 / 1M ms	$0.00
W7S usage guard reads	0	$0.50 / 1M	$0.00
W7S usage counter writes	0	$5.00 / 1M	$0.00
W7S operating margin	50% gross margin	price target	$0.00

This is a planning estimate, not a bill. It subtracts the included free-tier baseline first, estimates app usage plus W7S routing and usage-accounting overhead, then applies a 50% gross margin to the billable overage; actual hosted W7S pricing can differ.

How To Read This

The calculator estimates monthly W7S usage from traffic, storage, queues, logs, and stateful backend features. It also includes W7S platform overhead for routing, usage enforcement, usage counters, log handling, and other control-plane work. It is useful for planning, quota design, and understanding which features multiply cost. It is not a final hosted w7s.cloud bill.

Pick a startup stage first. Each stage sets the sliders to a common traffic and infrastructure shape, and every slider uses whole-number values. The Free tier stage is the included baseline and should estimate $0.00. Higher stages show billable overage above that baseline.

The estimate subtracts the included baseline first, estimates operating cost from the selected traffic shape, adds W7S overhead, then applies a 50% gross margin to the billable overage.

What Drives Cost

W7S area	Main cost driver	Why it matters
Public traffic	Runtime requests and CPU	W7S routes requests through the platform and app runtime. More requests and heavier handlers increase usage.
Static frontends	Asset storage and origin reads on cache misses	W7S stores deploy assets and caches immutable files. Better cache hit rates reduce origin reads.
Native backends	CPU milliseconds, storage reads/writes, logs	Expensive handlers, chatty data access, and noisy logging increase cost faster than simple request count.
Serverless DB and FS	Operation counts and stored GB-month	W7S can provision per-app DB, key-value, and FS bindings; database usage is included in the same usage model.
Queues	Operations per message	A normal delivered queue message is roughly one write, one read, and one delete. Retries add more reads.
Stateful coordination	Requests, active duration, and storage	Long-lived stateful workloads can dominate cost even if request volume is low.
Logs	Events written	W7S exposes app console and exception logs, but log volume should stay intentional.
W7S platform overhead	Routing, usage guards, counters, and log ingestion	W7S runs extra platform work around each app so deploys, public routing, quota enforcement, and observability keep working.

Pricing Notes

The calculator is a planning tool. It keeps provider details out of the user-facing estimate and shows W7S usage categories instead of infrastructure product names. The final estimate includes a 50% gross margin after W7S overhead, so the public price target is higher than raw infrastructure cost.

Free-Tier Policy

W7S also has its own free-tier guardrails. These are not billing-grade counters yet; they are operational protections that keep one app, owner, or global account from burning through shared infrastructure unexpectedly.

Use the Usage Accounting API to inspect daily usage, warning thresholds, daily caps, hourly resource usage, and the GitHub issue workflow that reports quota pressure back to the repository.