Two pricing tracks: projects and subscriptions
Infrastructure is quoted per project; products run on SaaS tiers. Entry prices assume low complexity and mark the smallest useful engagement — they are not a flat package. A formal quote separates one-time delivery, monthly maintenance, and third-party resources. Cost, capacity, and responsibility are written down before implementation.
From diagnosis to long-term operations
Entry prices show the smallest useful engagement. A formal quote separates one-time delivery, recurring maintenance, and third-party resources.
Resource fees and implementation billed separately; customer-owned cloud accounts preferred.
SaaS & SMS products
Per-product tiers: start free, scale by seats and usage, private deployment quoted separately.
Tier prices ship with each product release. Currently invite-only trial; details confirmed through assessment.
One-time delivery
Implementation after diagnosis: deployment, domains and TLS, cache, forms, migration, launch verification.
Monthly maintenance
Agreed checks, certificates, backup state, health, alert response, small changes. Response windows defined first.
Third-party resources
Servers, CDN, object storage, transcoding, video traffic, mail, domains — billed separately by providers, not bundled.
Custom work outside scope
Membership, payment, complex permissions, large migration, performance, security review — assessed before execution, not hidden in a fixed price.
| Variable | Why it changes effort | How a quote states it |
|---|---|---|
| Target regions | Determines placement, network verification, possible data requirements | List primary regions and test scope |
| Content & traffic | Images, video, downloads, dynamic requests have different economics | State capacity, monthly traffic, peak, growth assumptions |
| Existing systems | Migration, legacy URLs, databases, integrations add dependencies | List migrated objects, downtime, owners |
| Operating responsibility | Check frequency, response, recovery targets set recurring effort | Define coverage, exclusions, out-of-scope handling |
Why do prices say “from” or “scoped”?
Entry work assumes low complexity. Regions, volume, legacy systems, and responsibility materially change effort; one fixed number would hide work or shrink delivery.
Is there a fee before a formal quote?
Ordinary discussion and directional review are not automatically paid. Access-heavy assessment, formal reports, or performance testing are scoped and priced first.
Who pays the cloud providers?
Customer-owned accounts with direct billing are preferred for control and transparency. Managed billing states limits, payment, and exit handling.
Can we begin with a small validation?
Yes. A single site, region, content class, or recovery exercise produces real evidence. Validation still has acceptance and stop conditions.
Does a low-cost launch include maintenance?
No. One-time launch and ongoing ownership are separate. A launch-only scope states who handles certificates, backups, alerts, and changes afterward.