From 9ef7212a3e394a10bdabc121b338b0bb563234e2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mat=C4=9Bj=20Pavl=C3=AD=C4=8Dek?= Date: Tue, 27 Oct 2026 21:48:28 +0100 Subject: [PATCH] z0 - update billing section, project start/stop, assign/release ipv4 --- .../content/alpine/how-to/build-process.mdx | 2 +- .../payment.mdx => billing/overview.mdx} | 94 ++- .../content/{company => billing}/pricing.mdx | 8 +- .../content/deno/how-to/build-process.mdx | 2 +- apps/docs/content/features/backup.mdx | 7 +- apps/docs/content/features/infrastructure.mdx | 4 +- apps/docs/content/features/pipeline.mdx | 2 +- apps/docs/content/features/scaling.mdx | 2 +- apps/docs/content/guides/backup.mdx | 7 +- apps/docs/content/guides/networking.mdx | 2 +- apps/docs/content/guides/public-access.mdx | 2 +- apps/docs/content/help/faq.mdx | 2 +- apps/docs/content/keydb/how-to/scale.mdx | 2 +- apps/docs/content/mariadb/how-to/scale.mdx | 2 +- apps/docs/content/postgresql/how-to/scale.mdx | 2 +- .../references/networking/public-access.mdx | 10 +- .../content/ubuntu/how-to/build-process.mdx | 2 +- apps/docs/content/zbox/pricing.mdx | 4 +- apps/docs/sidebars.js | 48 +- .../components/PricingCalculator/index.tsx | 8 +- .../src/components/content/build-process.mdx | 2 +- .../src/components/content/create-scaling.mdx | 2 +- apps/docs/src/components/content/scaling.mdx | 2 +- apps/docs/static/llms-full.txt | 639 ++++++++++-------- apps/docs/static/llms-small.txt | 43 +- apps/docs/static/llms.txt | 6 +- zerops-llm-script.ts | 4 +- zerops.yml | 28 + 28 files changed, 539 insertions(+), 399 deletions(-) rename apps/docs/content/{company/payment.mdx => billing/overview.mdx} (50%) rename apps/docs/content/{company => billing}/pricing.mdx (93%) diff --git a/apps/docs/content/alpine/how-to/build-process.mdx b/apps/docs/content/alpine/how-to/build-process.mdx index d28b59cd..e9d16e4e 100644 --- a/apps/docs/content/alpine/how-to/build-process.mdx +++ b/apps/docs/content/alpine/how-to/build-process.mdx @@ -99,7 +99,7 @@ Build containers start with minimum resources and scale vertically up to maximum The time limit for the whole build pipeline is **1 hour**. After 1 hour, Zerops will terminate the build pipeline and delete the build container. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ## Troubleshooting builds diff --git a/apps/docs/content/company/payment.mdx b/apps/docs/content/billing/overview.mdx similarity index 50% rename from apps/docs/content/company/payment.mdx rename to apps/docs/content/billing/overview.mdx index 3e6cc944..69d02b2a 100644 --- a/apps/docs/content/company/payment.mdx +++ b/apps/docs/content/billing/overview.mdx @@ -1,13 +1,88 @@ --- -title: Top-up & Billing -description: Understanding credits, payment methods, and automatic top-ups in Zerops. +title: Billing +description: How Zerops charges your credit, how project core and dedicated IPv4 subscriptions renew, how to start a stopped project, and how to top up. --- import { Dropdown, DropdownItem } from '/src/components/Dropdown'; -Zerops provides a transparent credit-based payment system that makes managing your account finances straightforward. You can easily add funds to your account through manual or automatic top-ups, track all your transactions, and download invoices for your records. +Zerops is prepaid. You top up credit, and Zerops charges your projects, services and add-ons from it. You can add funds manually or automatically, track all your transactions, and download invoices for your records. -This page explains how to manage your account balance, set up payment preferences, and access your complete billing history to help you maintain uninterrupted service while keeping your finances organized. +This page explains how charges and subscriptions work, what happens when your credit runs out, and how to manage top-ups and invoices. For the prices themselves, see [Pricing](/billing/pricing). + +## Credit + +Your organization has two balances, both shown in **Credit & Spend Overview** in the Organization section of the main menu: + +- **Credit** - the money you top up, manually or [automatically](#automatic-top-ups). +- **Promo credit** - credit granted by Zerops, for example on sign-up. Every [refund](#subscriptions) is paid out as promo credit too. + +Every charge takes promo credit first, then credit. + +Resource usage (CPU, RAM, disk and overages) is billed by the minute and deducted from your credit hourly. [Subscriptions](#subscriptions) are charged a month in advance. + +Your credit can drop below zero, because a subscription renewal always goes through. Your next top-up pays off the negative balance. + +## Subscriptions + +The [project core](#project-core) and a [dedicated IPv4 address](#dedicated-ipv4-address) are monthly subscriptions: + +- A period starts the moment the subscription is created and lasts one month. Periods don't follow calendar months: a subscription created on 14 March at 10:00 renews on 14 April at 10:00. +- At each renewal, Zerops charges the next month in advance. The renewal goes through even if it takes your credit below zero. +- You get a notification about every renewal. +- Every refund is paid out as promo credit, whether the period was paid with credit or promo credit. + +### Project Core + +Every project has a core subscription, either Lightweight or Serious. See [project core options](/features/infrastructure#project-core-options) for what each includes and [Pricing](/billing/pricing#project-core-plans) for the prices. + +- Creating a project charges the first month of its core. Zerops refuses to create the project if your balance (credit + promo credit) would not stay above zero after that charge. +- The core is charged for as long as the project exists, a stopped project included. +- [Upgrading the core](/features/infrastructure#project-core-upgrade) ends the current core subscription and refunds its unused rest pro rata as promo credit. The new core subscription starts at that moment, and its first month is charged. +- Deleting a project ends its core subscription and refunds the unused rest pro rata as promo credit. + +### Dedicated IPv4 Address + +A dedicated IPv4 address is a project add-on, called **unique IPv4 address** in the GUI. See [Public Access Configuration](/references/networking/public-access#ipv4-configuration) for what it is for and [Pricing](/billing/pricing#additional-services) for the price. A project can have one dedicated IPv4 address. + +#### Activate + +You can activate a dedicated IPv4 address when: + +- the project is active or is being created, +- your organization has made at least one top-up, and +- your balance covers the first month, unless you [reuse a paid period](#reuse-a-paid-period). + +Activate it in the project's IP access settings or in the **Add-ons** section of the project. The GUI shows the price per month and the dates of the first period. The first month is charged right away, and the subscription then renews every month. The fee is never refunded. + +#### Release + +A dedicated IPv4 address is released when: + +- you click **Release IPv4 address** in the **Add-ons** section of the project, +- you delete the project, or +- Zerops [stops the project](#when-credit-runs-out). + +The address is removed from the project right away, and the project falls back to the shared IPv4. The paid period stays with your organization until it ends. + +#### Reuse a Paid Period + +If you activate a dedicated IPv4 address on any project of your organization before a released period ends, Zerops reuses that period at no extra charge. The GUI shows this as **Reuse paid IPv4 address**. The period keeps its end date, and the next renewal is charged as usual. + +The project gets an address that may differ from the released one, so check the DNS A records of your domains. A period that you don't reuse expires at its end, and nothing more is charged for it. + +## When Credit Runs Out + +Zerops may stop the projects of an organization that has run out of credit. When Zerops stops a project: + +- its services stop, +- its dedicated IPv4 address is [released](#release), and +- its core is still charged, because the project still exists. + +A stopped project stays stopped after a top-up. Start it with **Start project** on the project in the GUI, or with `PUT /project/{id}/start` in the [public API](/references/api). Zerops starts the project only if your balance (credit + promo credit) is above zero. If it isn't, the GUI asks you to top up credit first. + +Starting the project doesn't bring back its dedicated IPv4 address. Activate it again: while the released period lasts, it is [reused at no extra charge](#reuse-a-paid-period). + +Enable [automatic top-ups](#automatic-top-ups) to keep your credit above zero. ## Manual Top-up @@ -80,17 +155,6 @@ The maximum total that can be automatically charged within a single calendar mon -## When Credit Runs Out - -Resource usage is deducted from your credit hourly, while subscriptions such as the project core and a dedicated IPv4 address are charged for a month in advance and renewed on the day they were activated. - -If your credit cannot cover a renewal: - -- The renewal fails and you are notified in the dashboard. -- A dedicated IPv4 address is released and the project falls back to the shared IPv4. The subscription is not restored automatically after a top-up; add the address again from the project's routing settings once credit is available, which starts a new paid month. - -Enable [automatic top-ups](#automatic-top-ups) to avoid failed renewals. - ## Billing Information You are required to enter billing details for all transactions (manual and automatic top-ups), with one exception: diff --git a/apps/docs/content/company/pricing.mdx b/apps/docs/content/billing/pricing.mdx similarity index 93% rename from apps/docs/content/company/pricing.mdx rename to apps/docs/content/billing/pricing.mdx index a7e796f5..8ae03e91 100644 --- a/apps/docs/content/company/pricing.mdx +++ b/apps/docs/content/billing/pricing.mdx @@ -11,7 +11,7 @@ The total cost of deploying an application includes your project's **core packag Resources are allocated per service and billed by the minute, though credit is deducted hourly based on actual usage. You're only charged for what you use, calculated down to the minute. ::: -Need to add credits to your account? Visit our [Top-up & Billing page](/company/payment) for instructions. +Zerops is prepaid: you top up credit and Zerops charges it. The project core and a dedicated IPv4 address are monthly subscriptions. See [Billing](/billing/overview) for how charges, renewals and refunds work, and how to top up. ## Project Core Plans @@ -25,7 +25,7 @@ Best for development, testing, and smaller workloads with limited redundancy. - **Backup Storage**: 5 GB - **Egress Traffic**: 100 GB per month -### Serious Core - $10 / 30 days +### Serious Core - $10 per month Optimized for production workloads with high availability and comprehensive failover protection. **Included resources:** @@ -95,11 +95,11 @@ Enhance your deployment with these optional services to meet specific requiremen Dedicated IPv4 $3.00 per month - Exclusive IPv4 address for your project (instead of shared) + Exclusive IPv4 address for your project (instead of shared), billed as a monthly subscription Object Storage - $0.01 per GB / 30 days + $0.02 per GB / 30 days Scalable storage for files, backups, and static assets diff --git a/apps/docs/content/deno/how-to/build-process.mdx b/apps/docs/content/deno/how-to/build-process.mdx index f730e456..08a54d99 100644 --- a/apps/docs/content/deno/how-to/build-process.mdx +++ b/apps/docs/content/deno/how-to/build-process.mdx @@ -84,7 +84,7 @@ All runtime services use the same hardware resources for build containers: Build containers start with minimum resources and scale vertically up to maximum capacity as needed. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ### Build time limit diff --git a/apps/docs/content/features/backup.mdx b/apps/docs/content/features/backup.mdx index 9a115246..986c7764 100644 --- a/apps/docs/content/features/backup.mdx +++ b/apps/docs/content/features/backup.mdx @@ -129,10 +129,7 @@ Each Zerops project has a **technical maximum backup storage limit of 1 TiB**: - This quota is shared across all service backups within the project ### Billing -- **Lightweight Project Core**: 5 GB backup storage and 100 GB egress included -- **Serious Project Core**: 25 GB backup storage and 3 TB egress included - -When you exceed your plan's free limits, **additional charges apply** according to our [pricing](/company/pricing#overage-costs). +Each [project core plan](/billing/pricing#project-core-plans) includes some backup storage and egress. When you exceed your plan's free limits, **additional charges apply** according to our [pricing](/billing/pricing#overage-costs). ### Retention Policy and Configuration @@ -240,7 +237,7 @@ When a project is deleted, the encryption key is permanently destroyed after 7 d 1. **Review & Prune**: Delete unnecessary manual backups or remove protected status from older backups 2. **Adjust Retention Policy**: Reduce minimum retention counts if your recovery requirements allow 3. **Optimize Schedule**: Reduce backup frequency if daily backups aren't essential -4. **Monitor Costs**: Check usage against your free tier (5GB/25GB) to avoid unexpected overage charges +4. **Monitor Costs**: Check usage against the backup storage included in your [project core plan](/billing/pricing#project-core-plans) to avoid unexpected overage charges 5. **Contact Support**: If you need assistance managing storage ### Backup Failures diff --git a/apps/docs/content/features/infrastructure.mdx b/apps/docs/content/features/infrastructure.mdx index 03068bfe..8e5408bd 100644 --- a/apps/docs/content/features/infrastructure.mdx +++ b/apps/docs/content/features/infrastructure.mdx @@ -126,7 +126,7 @@ Production applications, high-traffic websites, mission-critical business applic -For detailed pricing information on both core types, visit our [pricing page](/company/pricing#project-core-plans). +For detailed pricing information on both core types, visit our [pricing page](/billing/pricing#project-core-plans). #### Project Core Upgrade @@ -139,7 +139,7 @@ The core upgrade is a **partially destructive process** that will temporarily di **What happens during upgrade:** - All project logs and statistics will be lost (forwarded logs/statistics are not affected) - Services will be network-unavailable during the process (avg. 35 seconds but can take longer) -- $10 project core fee will be charged upon upgrade +- The unused rest of the current core is refunded as promo credit, and the first month of Serious Core is charged (see [Billing](/billing/overview#project-core)) - Free project resources will reset to Serious Core limits - Project IP addresses remain unchanged diff --git a/apps/docs/content/features/pipeline.mdx b/apps/docs/content/features/pipeline.mdx index 1dbe5195..7fe3fcc6 100644 --- a/apps/docs/content/features/pipeline.mdx +++ b/apps/docs/content/features/pipeline.mdx @@ -195,7 +195,7 @@ All runtime services use the same hardware resources for build containers: Build containers start with minimum resources and scale vertically up to maximum capacity as needed. :::info -Build container resources are not charged. Build costs are covered by the standard Zerops [project fee](https://zerops.io/#pricing). +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ### Build time limit diff --git a/apps/docs/content/features/scaling.mdx b/apps/docs/content/features/scaling.mdx index 72896a6b..aa193f9b 100644 --- a/apps/docs/content/features/scaling.mdx +++ b/apps/docs/content/features/scaling.mdx @@ -124,7 +124,7 @@ Dedicated CPU gives exclusive access to a full physical CPU core(s), ensuring co CPU mode can be changed (once per hour) as needed. ::: -See the [pricing](/company/pricing#resource-pricing) for the difference between CPU modes. +See the [pricing](/billing/pricing#resource-pricing) for the difference between CPU modes. #### Minimum and Maximum CPU Cores diff --git a/apps/docs/content/guides/backup.mdx b/apps/docs/content/guides/backup.mdx index df915104..5fdedee6 100644 --- a/apps/docs/content/guides/backup.mdx +++ b/apps/docs/content/guides/backup.mdx @@ -25,11 +25,8 @@ MariaDB, PostgreSQL, Qdrant, NATS, Meilisearch, Local Storage, SeaweedFS. - **Protected tags**: Exempt from automatic deletion — use for critical snapshots ## Storage Limits -| Plan | Backup Storage | Egress | -|------|---------------|--------| -| Lightweight | 5 GB | 100 GB | -| Serious | 25 GB | 3 TB | -| Technical max | 1 TiB per project (shared across all services) | +- Included backup storage and egress depend on the project core: [pricing](/billing/pricing#project-core-plans) +- Technical max: 1 TiB per project (shared across all services) ## Retention Defaults - Minimum kept: 7 daily + 4 weekly + 3 monthly diff --git a/apps/docs/content/guides/networking.mdx b/apps/docs/content/guides/networking.mdx index 6087e634..4bcd3b41 100644 --- a/apps/docs/content/guides/networking.mdx +++ b/apps/docs/content/guides/networking.mdx @@ -99,7 +99,7 @@ Work through these steps **in order**: | Feature | Shared IPv4 | Dedicated IPv4 | |---------|-------------|----------------| -| Cost | Free | $3 / 30 days | +| Cost | Free | $3 per month ([billing](/billing/overview#dedicated-ipv4-address)) | | Protocol support | HTTP/HTTPS only | All (TCP/UDP/HTTP) | | Connections | Limited, shorter timeouts | Full capacity | | Blacklist risk | Shared with other users | Isolated | diff --git a/apps/docs/content/guides/public-access.mdx b/apps/docs/content/guides/public-access.mdx index eb3208a5..ed62bb22 100644 --- a/apps/docs/content/guides/public-access.mdx +++ b/apps/docs/content/guides/public-access.mdx @@ -31,4 +31,4 @@ Zerops offers three public access methods: zerops.app subdomains (dev only, 50MB - Configurable firewall: blacklist or whitelist per port ## Gotchas -1. **Dedicated IPv4 is non-refundable**: $3/month, auto-renews — the fee isn't refunded if removed early, but the address can be reused in another project until the subscription ends. If a renewal fails for lack of credit, the address is released and must be added again after a top-up +1. **Dedicated IPv4 is a monthly subscription, never refunded**: $3 per month. Releasing it frees the address right away, and a new activation may get a different address, so update the DNS A records. Activation, release and reuse of a paid period: [Billing](/billing/overview#dedicated-ipv4-address) diff --git a/apps/docs/content/help/faq.mdx b/apps/docs/content/help/faq.mdx index 2ca08f2a..d88ad22c 100644 --- a/apps/docs/content/help/faq.mdx +++ b/apps/docs/content/help/faq.mdx @@ -17,7 +17,7 @@ Get quick answers to your related questions about Zerops from frequently asked q It's free to get started, and no credit card is required! However, we - recommend visiting our pricing page to explore the options that best suit your needs. + recommend visiting our pricing page to explore the options that best suit your needs. We also have a calculator on our pricing page that can help you estimate the cost of your project. diff --git a/apps/docs/content/keydb/how-to/scale.mdx b/apps/docs/content/keydb/how-to/scale.mdx index 3d09e82e..b00a57e3 100644 --- a/apps/docs/content/keydb/how-to/scale.mdx +++ b/apps/docs/content/keydb/how-to/scale.mdx @@ -35,7 +35,7 @@ You can configure scaling settings: /> -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your KeyDB service: diff --git a/apps/docs/content/mariadb/how-to/scale.mdx b/apps/docs/content/mariadb/how-to/scale.mdx index fd4d300c..147a5d35 100644 --- a/apps/docs/content/mariadb/how-to/scale.mdx +++ b/apps/docs/content/mariadb/how-to/scale.mdx @@ -35,7 +35,7 @@ You can configure scaling settings: /> -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your MariaDB service: diff --git a/apps/docs/content/postgresql/how-to/scale.mdx b/apps/docs/content/postgresql/how-to/scale.mdx index 47c77cc3..28834fe7 100644 --- a/apps/docs/content/postgresql/how-to/scale.mdx +++ b/apps/docs/content/postgresql/how-to/scale.mdx @@ -278,7 +278,7 @@ You can configure scaling settings: /> -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your PostgreSQL service: diff --git a/apps/docs/content/references/networking/public-access.mdx b/apps/docs/content/references/networking/public-access.mdx index 3166a27b..41ad1827 100644 --- a/apps/docs/content/references/networking/public-access.mdx +++ b/apps/docs/content/references/networking/public-access.mdx @@ -74,13 +74,13 @@ Before setting up domain access, you need to configure public IP addresses. Zero #### IPv4 Configuration -**Dedicated IPv4 Address ($3/month)** +**Dedicated IPv4 Address ($3 per month)** - Dedicated to your project and shared across all project services - One IPv4 address per project limit - Protects against blacklisting risks associated with shared IPs -- Subscription automatically renews every month on the day it was activated *(cannot be purchased with promo credit)* -- If the renewal cannot be paid, the address is released and the project falls back to the shared IPv4. Topping up does not restore it; add the address again once credit is available (see [Top-up & Billing](/company/payment#when-credit-runs-out)) -- Fee is non-refundable but address can be reused in another project until subscription ends +- Called **unique IPv4 address** in the GUI, available on an active project once your organization has made a top-up +- Monthly subscription, never refunded. A released address leaves a paid period that you can reuse on any of your projects, see [Billing](/billing/overview#dedicated-ipv4-address) +- When released, the project falls back to the shared IPv4. A new activation may get a different address, so check your DNS A records - **Recommended for production workloads** **Shared IPv4 Address (Free)** @@ -198,7 +198,7 @@ Currently, direct public port access is only available for runtime services and - For PostgreSQL services: Select **Direct access through IP address** - Or access from project's **Project & Services Access Overview** section → **Direct IP Accesses to Services** 2. Configure port settings: - - Either **Setup first access through IPv6** or activate **Unique IPv4 add-on** (if needed) + - Either **Setup first access through IPv6** or activate a **unique IPv4 address** (if needed) - Choose any port from 10-65435 (ports 80 and 443 are reserved) - Select destination service and internal port - Each public port can be mapped to any internal service port diff --git a/apps/docs/content/ubuntu/how-to/build-process.mdx b/apps/docs/content/ubuntu/how-to/build-process.mdx index 48e19123..979b113c 100644 --- a/apps/docs/content/ubuntu/how-to/build-process.mdx +++ b/apps/docs/content/ubuntu/how-to/build-process.mdx @@ -99,7 +99,7 @@ Build containers start with minimum resources and scale vertically up to maximum The time limit for the whole build pipeline is **1 hour**. After 1 hour, Zerops will terminate the build pipeline and delete the build container. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ## Troubleshooting builds diff --git a/apps/docs/content/zbox/pricing.mdx b/apps/docs/content/zbox/pricing.mdx index b52abb7a..31450ea7 100644 --- a/apps/docs/content/zbox/pricing.mdx +++ b/apps/docs/content/zbox/pricing.mdx @@ -3,12 +3,12 @@ title: Pricing description: A Box Workspace is billed like any other Zerops service, for the CPU, RAM and disk of its VM, and everything inside it costs nothing extra. --- -Zerops Box has no price of its own. You pay for the Box Workspace service like for any other Zerops service, at the rates on the [Zerops pricing](/company/pricing) page. +Zerops Box has no price of its own. You pay for the Box Workspace service like for any other Zerops service, at the rates on the [Zerops pricing](/billing/pricing) page. ## What you pay for - **The workspace VM's resources.** A workspace has fixed resources and never autoscales, so you pay for the CPU cores, RAM and disk you [set](/zbox/workspace-service#resizing), whether sandboxes use them or not. CPU is billed at the shared or dedicated rate, depending on the CPU mode, shared unless you choose dedicated. -- **The project.** The project core, and optional extras such as a dedicated IPv4 address or egress over the included amount, are billed per project as usual ([pricing](/company/pricing), [top-up and billing](/company/payment)). +- **The project.** The project core, and optional extras such as a dedicated IPv4 address or egress over the included amount, are billed per project as usual ([pricing](/billing/pricing), [billing](/billing/overview)). ## What costs nothing extra diff --git a/apps/docs/sidebars.js b/apps/docs/sidebars.js index 1989cefd..6b4c3853 100644 --- a/apps/docs/sidebars.js +++ b/apps/docs/sidebars.js @@ -997,6 +997,32 @@ module.exports = { }, ], }, + { + type: 'html', + value: 'Pricing & Billing', + customProps: { + sidebar_is_group_divider: true, + }, + className: 'homepage-sidebar-item', + }, + { + type: 'doc', + id: 'billing/pricing', + label: 'Pricing', + customProps: { + sidebar_icon: 'currency-dollar', + }, + className: 'homepage-sidebar-item', + }, + { + type: 'doc', + id: 'billing/overview', + label: 'Billing', + customProps: { + sidebar_icon: 'receipt-percent', + }, + className: 'homepage-sidebar-item', + }, { type: 'html', value: 'Help', @@ -1040,28 +1066,6 @@ module.exports = { }, className: 'homepage-sidebar-item', }, - { - type: 'category', - link: { - type: 'doc', - id: 'company/pricing', - }, - label: 'Pricing', - customProps: { - sidebar_icon: 'currency-dollar', - }, - className: 'homepage-sidebar-item', - items: [ - { - type: 'doc', - id: 'company/payment', - label: 'Top-up & Billing', - customProps: { - exclude_from_doc_list: false, - }, - }, - ], - }, { type: 'doc', id: 'company/branding', diff --git a/apps/docs/src/components/PricingCalculator/index.tsx b/apps/docs/src/components/PricingCalculator/index.tsx index 3bdfd9fb..db8c7011 100644 --- a/apps/docs/src/components/PricingCalculator/index.tsx +++ b/apps/docs/src/components/PricingCalculator/index.tsx @@ -96,7 +96,7 @@ function PricingCalculatorContent() { cpu: resources.cpuType === 'shared' ? 0.6 : 6, ram: 3, disk: 0.1, - storage: 0.01, + storage: 0.02, ipv4_addr: 3, backup: 0.1, buildTime: 0.033, @@ -382,7 +382,7 @@ const exportToPDF = () => { // Disk addText('Disk', margin + 5, y, { color: secondaryTextColor, size: 9 }); - addText(`(${service.disk}GB × ${service.nodes} nodes) @ $0.05/GB = $${formatNumber(resourceCosts.disk)}`, + addText(`(${service.disk}GB × ${service.nodes} nodes) @ $${price.disk.toFixed(2)}/GB = $${formatNumber(resourceCosts.disk)}`, pageWidth - margin - 5, y, { align: 'right', color: secondaryTextColor, @@ -510,7 +510,7 @@ const exportToPDF = () => { >
Lightweight
- $0/30 days + $0/month
Single-container core services with modest build hours, backup storage, and egress bandwidth included. Ideal for development and smaller production projects. @@ -523,7 +523,7 @@ const exportToPDF = () => { >
Serious
- $10/30 days + $10/month
Highly available core services with generous build hours, backup storage, and egress bandwidth included. Perfect for production workloads that mean business. diff --git a/apps/docs/src/components/content/build-process.mdx b/apps/docs/src/components/content/build-process.mdx index 88ea312b..a39269a7 100644 --- a/apps/docs/src/components/content/build-process.mdx +++ b/apps/docs/src/components/content/build-process.mdx @@ -86,7 +86,7 @@ Build containers start with minimum resources and scale vertically up to maximum The time limit for the whole build pipeline is **1 hour**. After 1 hour, Zerops will terminate the build pipeline and delete the build container. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ## Troubleshooting builds diff --git a/apps/docs/src/components/content/create-scaling.mdx b/apps/docs/src/components/content/create-scaling.mdx index fa4a2e73..2aa463c1 100644 --- a/apps/docs/src/components/content/create-scaling.mdx +++ b/apps/docs/src/components/content/create-scaling.mdx @@ -37,5 +37,5 @@ These settings can significantly improve application performance and reliability For detailed scaling configuration, troubleshooting, and best practices, see: - How Zerops scales - Service-specific scaling guide - [Automatic Scaling and High Availability](/features/scaling) - Complete technical details -- [Zerops Pricing](https://zerops.io/#pricing) - Cost differences between CPU modes and resource usage rates +- [Zerops Pricing](/billing/pricing#resource-pricing) - Cost differences between CPU modes and resource usage rates ::: \ No newline at end of file diff --git a/apps/docs/src/components/content/scaling.mdx b/apps/docs/src/components/content/scaling.mdx index 9bf55348..82d3a9f6 100644 --- a/apps/docs/src/components/content/scaling.mdx +++ b/apps/docs/src/components/content/scaling.mdx @@ -40,7 +40,7 @@ You can configure scaling settings at different stages: ### CPU Settings -**CPU mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs or read more about [CPU mode](/features/scaling#cpu-mode). +**CPU mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs or read more about [CPU mode](/features/scaling#cpu-mode). **Minimum and Maximum CPU**: Configure the boundaries for CPU core allocation. Zerops will scale CPU resources within these limits based on actual usage. diff --git a/apps/docs/static/llms-full.txt b/apps/docs/static/llms-full.txt index c8ec48d1..5dd36289 100644 --- a/apps/docs/static/llms-full.txt +++ b/apps/docs/static/llms-full.txt @@ -3839,12 +3839,12 @@ A **connector** is a ready-made provider login (Claude Code, GitHub, OpenAI Code # Zbox > Pricing -Zerops Box has no price of its own. You pay for the Box Workspace service like for any other Zerops service, at the rates on the [Zerops pricing](/company/pricing) page. +Zerops Box has no price of its own. You pay for the Box Workspace service like for any other Zerops service, at the rates on the [Zerops pricing](/billing/pricing) page. ## What you pay for - **The workspace VM's resources.** A workspace has fixed resources and never autoscales, so you pay for the CPU cores, RAM and disk you [set](/zbox/workspace-service#resizing), whether sandboxes use them or not. CPU is billed at the shared or dedicated rate, depending on the CPU mode, shared unless you choose dedicated. -- **The project.** The project core, and optional extras such as a dedicated IPv4 address or egress over the included amount, are billed per project as usual ([pricing](/company/pricing), [top-up and billing](/company/payment)). +- **The project.** The project core, and optional extras such as a dedicated IPv4 address or egress over the included amount, are billed per project as usual ([pricing](/billing/pricing), [billing](/billing/overview)). ## What costs nothing extra @@ -6247,7 +6247,7 @@ Build containers start with minimum resources and scale vertically up to maximum The time limit for the whole build pipeline is **1 hour**. After 1 hour, Zerops will terminate the build pipeline and delete the build container. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ## Troubleshooting builds @@ -15597,13 +15597,13 @@ Before setting up domain access, you need to configure public IP addresses. Zero #### IPv4 Configuration -**Dedicated IPv4 Address ($3/month)** +**Dedicated IPv4 Address ($3 per month)** - Dedicated to your project and shared across all project services - One IPv4 address per project limit - Protects against blacklisting risks associated with shared IPs -- Subscription automatically renews every month on the day it was activated *(cannot be purchased with promo credit)* -- If the renewal cannot be paid, the address is released and the project falls back to the shared IPv4. Topping up does not restore it; add the address again once credit is available (see [Top-up & Billing](/company/payment#when-credit-runs-out)) -- Fee is non-refundable but address can be reused in another project until subscription ends +- Called **unique IPv4 address** in the GUI, available on an active project once your organization has made a top-up +- Monthly subscription, never refunded. A released address leaves a paid period that you can reuse on any of your projects, see [Billing](/billing/overview#dedicated-ipv4-address) +- When released, the project falls back to the shared IPv4. A new activation may get a different address, so check your DNS A records - **Recommended for production workloads** **Shared IPv4 Address (Free)** @@ -15705,7 +15705,7 @@ Currently, direct public port access is only available for runtime services and - For PostgreSQL services: Select **Direct access through IP address** - Or access from project's **Project & Services Access Overview** section → **Direct IP Accesses to Services** 2. Configure port settings: - - Either **Setup first access through IPv6** or activate **Unique IPv4 add-on** (if needed) + - Either **Setup first access through IPv6** or activate a **unique IPv4 address** (if needed) - Choose any port from 10-65435 (ports 80 and 443 are reserved) - Select destination service and internal port - Each public port can be mapped to any internal service port @@ -21159,7 +21159,7 @@ You can configure scaling settings: ### Basic settings -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your PostgreSQL service: @@ -27676,7 +27676,7 @@ You can configure scaling settings: ### Basic settings -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your MariaDB service: @@ -29135,7 +29135,7 @@ You can configure scaling settings: ### Basic settings -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your KeyDB service: @@ -31212,7 +31212,7 @@ You can access the Zerops Dashboard GUI directly at [app.zerops.io](https://app. **Question: How much does it cost to get started?** It's free to get started, and no credit card is required! However, we - recommend visiting our [pricing page](/company/pricing) to explore the options that best suit your needs. + recommend visiting our [pricing page](/billing/pricing) to explore the options that best suit your needs. We also have a calculator on our pricing page that can help you estimate the cost of your project. @@ -31985,7 +31985,7 @@ Zerops offers three public access methods: zerops.app subdomains (dev only, 50MB - Configurable firewall: blacklist or whitelist per port ## Gotchas -1. **Dedicated IPv4 is non-refundable**: $3/month, auto-renews — the fee isn't refunded if removed early, but the address can be reused in another project until the subscription ends. If a renewal fails for lack of credit, the address is released and must be added again after a top-up +1. **Dedicated IPv4 is a monthly subscription, never refunded**: $3 per month. Releasing it frees the address right away, and a new activation may get a different address, so update the DNS A records. Activation, release and reuse of a paid period: [Billing](/billing/overview#dedicated-ipv4-address) ---------------------------------------- @@ -32489,7 +32489,7 @@ Work through these steps **in order**: | Feature | Shared IPv4 | Dedicated IPv4 | |---------|-------------|----------------| -| Cost | Free | $3 / 30 days | +| Cost | Free | $3 per month ([billing](/billing/overview#dedicated-ipv4-address)) | | Protocol support | HTTP/HTTPS only | All (TCP/UDP/HTTP) | | Connections | Limited, shorter timeouts | Full capacity | | Blacklist risk | Shared with other users | Isolated | @@ -33660,12 +33660,8 @@ MariaDB, PostgreSQL, Qdrant, NATS, Meilisearch, Local Storage, SeaweedFS. - **Protected tags**: Exempt from automatic deletion — use for critical snapshots ## Storage Limits -| Plan | Backup Storage | Egress | -|------|---------------|--------| -| Lightweight | 5 GB | 100 GB | -| Serious | 25 GB | 3 TB | -| Technical max | 1 TiB per project (shared across all services) | -| Technical max | 1 TiB per project (shared across all services) | +- Included backup storage and egress depend on the project core: [pricing](/billing/pricing#project-core-plans) +- Technical max: 1 TiB per project (shared across all services) ## Retention Defaults - Minimum kept: 7 daily + 4 weekly + 3 monthly @@ -36659,7 +36655,7 @@ Dedicated CPU gives exclusive access to a full physical CPU core(s), ensuring co CPU mode can be changed (once per hour) as needed. ::: -See the [pricing](/company/pricing#resource-pricing) for the difference between CPU modes. +See the [pricing](/billing/pricing#resource-pricing) for the difference between CPU modes. #### Minimum and Maximum CPU Cores @@ -37574,7 +37570,7 @@ All runtime services use the same hardware resources for build containers: Build containers start with minimum resources and scale vertically up to maximum capacity as needed. :::info -Build container resources are not charged. Build costs are covered by the standard Zerops [project fee](https://zerops.io/#pricing). +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ### Build time limit @@ -38049,7 +38045,7 @@ Production applications, high-traffic websites, mission-critical business applic -For detailed pricing information on both core types, visit our [pricing page](/company/pricing#project-core-plans). +For detailed pricing information on both core types, visit our [pricing page](/billing/pricing#project-core-plans). #### Project Core Upgrade @@ -38062,7 +38058,7 @@ The core upgrade is a **partially destructive process** that will temporarily di **What happens during upgrade:** - All project logs and statistics will be lost (forwarded logs/statistics are not affected) - Services will be network-unavailable during the process (avg. 35 seconds but can take longer) -- $10 project core fee will be charged upon upgrade +- The unused rest of the current core is refunded as promo credit, and the first month of Serious Core is charged (see [Billing](/billing/overview#project-core)) - Free project resources will reset to Serious Core limits - Project IP addresses remain unchanged @@ -39807,10 +39803,7 @@ Each Zerops project has a **technical maximum backup storage limit of 1 TiB**: - This quota is shared across all service backups within the project ### Billing -- **Lightweight Project Core**: 5 GB backup storage and 100 GB egress included -- **Serious Project Core**: 25 GB backup storage and 3 TB egress included - -When you exceed your plan's free limits, **additional charges apply** according to our [pricing](/company/pricing#overage-costs). +Each [project core plan](/billing/pricing#project-core-plans) includes some backup storage and egress. When you exceed your plan's free limits, **additional charges apply** according to our [pricing](/billing/pricing#overage-costs). ### Retention Policy and Configuration @@ -39918,7 +39911,7 @@ When a project is deleted, the encryption key is permanently destroyed after 7 d 1. **Review & Prune**: Delete unnecessary manual backups or remove protected status from older backups 2. **Adjust Retention Policy**: Reduce minimum retention counts if your recovery requirements allow 3. **Optimize Schedule**: Reduce backup frequency if daily backups aren't essential -4. **Monitor Costs**: Check usage against your free tier (5GB/25GB) to avoid unexpected overage charges +4. **Monitor Costs**: Check usage against the backup storage included in your [project core plan](/billing/pricing#project-core-plans) to avoid unexpected overage charges 5. **Contact Support**: If you need assistance managing storage ### Backup Failures @@ -43913,7 +43906,7 @@ All runtime services use the same hardware resources for build containers: Build containers start with minimum resources and scale vertically up to maximum capacity as needed. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ### Build time limit @@ -44895,266 +44888,6 @@ zerops: Read more about how the [readiness check works](/deno/how-to/deploy-process#readiness-checks) in Zerops. ----------------------------------------- - -# Company > Pricing - - -Zerops provides a straightforward pricing structure based on your project type and resource usage. - -The total cost of deploying an application includes your project's **core package cost** + the **cost of the resources** of the services inside a project. Additional charges may apply for optional features such as dedicated IPv4, extra egress, object storage, extra backup space and extra build time. - -:::note Fair Billing Model -Resources are allocated per service and billed by the minute, though credit is deducted hourly based on actual usage. You're only charged for what you use, calculated down to the minute. -::: - -Need to add credits to your account? Visit our [Top-up & Billing page](/company/payment) for instructions. - -## Project Core Plans - -Zerops offers two core types to match different needs and budgets. For detailed information on both core types, visit our [Project & Services Structure](/features/infrastructure) page. - -### Lightweight Core - Free -Best for development, testing, and smaller workloads with limited redundancy. - -**Included resources:** -- **Build Time**: 15 hours per month -- **Backup Storage**: 5 GB -- **Egress Traffic**: 100 GB per month - -### Serious Core - $10 / 30 days -Optimized for production workloads with high availability and comprehensive failover protection. - -**Included resources:** -- **Build Time**: 150 hours per month -- **Backup Storage**: 25 GB -- **Egress Traffic**: 3 TB per month - -:::note Storage Limits -All projects have a technical maximum backup storage limit of **1 TiB**. Usage beyond the free tier allocation (5GB or 25GB) is billed according to the [overage costs](#overage-costs) below. -::: - -## Resource Pricing - -Services in Zerops require computing resources that are billed separately from your project core. These resources are allocated per service and billed by the minute based on actual usage, with credits deducted hourly. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ResourcePriceDescription
Shared CPU$0.60 per CPU / 30 daysEconomical option for most workloads with good performance
Dedicated CPU$6.00 per CPU / 30 daysReserved CPU cores for predictable performance
RAM$0.75 per 0.25 GB / 30 daysMemory allocated to your services
Disk Space$0.05 per 0.5 GB / 30 daysStorage space for your applications and data
- -:::note Daily Spending Control -You can set a daily spending limit in the GUI for your project to keep an eye on costs and avoid unexpected charges. This provides an alternative to configuring automatic resource scaling ranges while keeping your services running optimally. - -Reaching the limit does not stop your project - your services keep running. When a project reaches its daily spending limit, Zerops sends you a warning notification (e-mail) so you can decide whether to raise the limit. The limit resets at midnight (UTC). -::: - -## Additional Services - -Enhance your deployment with these optional services to meet specific requirements for networking, storage, and data transfer. - - - - - - - - - - - - - - - - - - - - - -
ServicePriceDescription
Dedicated IPv4$3.00 per monthExclusive IPv4 address for your project (instead of shared)
Object Storage$0.01 per GB / 30 daysScalable storage for files, backups, and static assets
- -## Overage Costs - -When you exceed the resources included in your project core plan, the following charges apply: - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemPriceDescription
Extra Egress$0.02 per GBData transfer out of your project beyond plan limits
Extra Backup Space$0.50 per 5 GBAdditional storage for automatic, encrypted backups
Extra Build Time$0.50 per 15 hoursAdditional time for building and deploying applications
- -## Pricing Calculator - -Use our pricing calculator to estimate your monthly costs based on your specific needs: - - ----------------------------------------- - -# Company > Payment - - -Zerops provides a transparent credit-based payment system that makes managing your account finances straightforward. You can easily add funds to your account through manual or automatic top-ups, track all your transactions, and download invoices for your records. - -This page explains how to manage your account balance, set up payment preferences, and access your complete billing history to help you maintain uninterrupted service while keeping your finances organized. - -## Manual Top-up - -Manual top-ups give you direct control over your account funding. To add credits to your account immediately: - -1. Navigate to **Credit & Spend Overview** in the Organization section of the main menu -2. Click on **Top up credit** and fill in the [billing information](#billing-information) -3. Enter your desired top-up amount (minimum $10 VAT excl.) -3. Complete payment using your saved or new payment method - -## Automatic Top-ups - -Automatic top-up ensures your projects continue running without interruption by replenishing your credits when they run low. - -:::note Prerequisites -Automatic top-ups are available once you have made at least one manual top-up, saved a payment method, and provided your [billing information](#billing-information). The saved card is charged off-session, so a valid payment method must stay on file. -::: - -To turn them on, navigate to **Credit & Spend Overview** in the Organization section of the main menu, open the automatic top-up settings, and configure the three values described below. - -### How Automatic Top-ups Work - -When enabled, Zerops periodically checks your balance and tops it up by a fixed amount whenever your credit drops below a threshold you choose, up to a limit you set for each calendar month. -Zerops initiates an automatic payment when: - -- Your combined balance (credit + promo credit) drops **below your threshold** -- You have automatic top-ups enabled -- The top-up wouldn't exceed your **calendar-month limit** - -:::note Important notes -- Each top-up charges the **fixed amount** you configured, regardless of how fast you're spending -- Your balance is checked periodically (every few minutes), so a top-up can take a few minutes to appear after you drop below the threshold -- The final automatic top-up of the month is reduced so the month's total lands exactly on your calendar-month limit; after the limit is reached, automatic top-ups pause until the next calendar month -- To avoid repeatedly hitting your payment method (which can get a card flagged or blocked by the payment processor), top-ups are spaced out: after a **successful** top-up Zerops waits **1 hour** before the next one, and after a **failed** top-up it waits **1 day** before trying again -- If a charge fails, Zerops notifies you so you can check the validity and available funds of your saved card. After **3 failed attempts in a row**, automatic top-up is turned off and you're notified by email; re-enable it once your payment method is working again -- Auto top-up limits don't affect manual payments — add any amount manually regardless of automatic settings -::: - -### Configuration Options - -#### Threshold -When your combined balance (credit + promo credit) drops below this value, an automatic top-up is triggered. - -#### Top-up Amount -The fixed amount charged to your saved card on each automatic top-up. - -- Minimum: $10 (matches the minimum manual payment) -- Maximum: $10,000 per top-up - -#### Calendar-Month Limit -The maximum total that can be automatically charged within a single calendar month (UTC). This safeguards against unexpected costs: once the limit is reached, automatic top-ups pause until the next calendar month. - -- Must be at least the top-up amount (so at least one top-up can go through each month) - -#### Real-World Example - -**Scenario:** Application with ~$50 weekly operating costs and an initial manual top-up of $100 - -**Your Settings:** -- Threshold = $50 -- Top-up amount = $200 -- Calendar-month limit = $500 - -**Expected behavior:** -- When your balance falls below $50, Zerops charges $200 to bring it back up -- Each top-up is exactly $200, no matter how fast you're spending, until you approach the calendar-month limit -- After two top-ups ($400), a full $200 would exceed the $500 limit, so the next top-up is reduced to $100, bringing the month's total to exactly $500 -- Automatic top-ups then pause until the limit resets at the start of the next calendar month (UTC) - -## When Credit Runs Out - -Resource usage is deducted from your credit hourly, while subscriptions such as the project core and a dedicated IPv4 address are charged for a month in advance and renewed on the day they were activated. - -If your credit cannot cover a renewal: - -- The renewal fails and you are notified in the dashboard. -- A dedicated IPv4 address is released and the project falls back to the shared IPv4. The subscription is not restored automatically after a top-up; add the address again from the project's routing settings once credit is available, which starts a new paid month. - -Enable [automatic top-ups](#automatic-top-ups) to avoid failed renewals. - -## Billing Information - -You are required to enter billing details for all transactions (manual and automatic top-ups), with one exception: - -- EU-based users who are not VAT payers with transactions under $350 - -You can save your billing details by navigating to **Invoices & Billing Settings** in the Organization section of the main menu. - -## Invoices - -Zerops provides easy access to all invoices generated for manual and automatic top-ups within your organization. - -To view and manage your invoices navigate to **Invoices & Billing Settings** in the Organization section of the main menu. - -## Export Credit Consumption Records - -Zerops allows you to download monthly reports of your credit consumption history for analysis and record-keeping. - -1. Navigate to **Credit & Spend Overview** in the Organization section -2. Find the **Export Credit Consumption Records** section -3. Click on any month button to download that period's report - -Reports are available for the past 12 months in TXT format and include: -- Client information and reporting period -- Starting and ending balances -- Itemized resource charges by project and service -- Credit transactions (top-ups, refunds, promotional credits) -- Clear distinction between common (paid) and promotional credits - ---------------------------------------- # Company > Branding @@ -46880,6 +46613,330 @@ zerops: Read more about how the [readiness check works](deploy-process#readiness-checks) in Zerops. +---------------------------------------- + +# Billing > Pricing + + +Zerops provides a straightforward pricing structure based on your project type and resource usage. + +The total cost of deploying an application includes your project's **core package cost** + the **cost of the resources** of the services inside a project. Additional charges may apply for optional features such as dedicated IPv4, extra egress, object storage, extra backup space and extra build time. + +:::note Fair Billing Model +Resources are allocated per service and billed by the minute, though credit is deducted hourly based on actual usage. You're only charged for what you use, calculated down to the minute. +::: + +Zerops is prepaid: you top up credit and Zerops charges it. The project core and a dedicated IPv4 address are monthly subscriptions. See [Billing](/billing/overview) for how charges, renewals and refunds work, and how to top up. + +## Project Core Plans + +Zerops offers two core types to match different needs and budgets. For detailed information on both core types, visit our [Project & Services Structure](/features/infrastructure) page. + +### Lightweight Core - Free +Best for development, testing, and smaller workloads with limited redundancy. + +**Included resources:** +- **Build Time**: 15 hours per month +- **Backup Storage**: 5 GB +- **Egress Traffic**: 100 GB per month + +### Serious Core - $10 per month +Optimized for production workloads with high availability and comprehensive failover protection. + +**Included resources:** +- **Build Time**: 150 hours per month +- **Backup Storage**: 25 GB +- **Egress Traffic**: 3 TB per month + +:::note Storage Limits +All projects have a technical maximum backup storage limit of **1 TiB**. Usage beyond the free tier allocation (5GB or 25GB) is billed according to the [overage costs](#overage-costs) below. +::: + +## Resource Pricing + +Services in Zerops require computing resources that are billed separately from your project core. These resources are allocated per service and billed by the minute based on actual usage, with credits deducted hourly. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ResourcePriceDescription
Shared CPU$0.60 per CPU / 30 daysEconomical option for most workloads with good performance
Dedicated CPU$6.00 per CPU / 30 daysReserved CPU cores for predictable performance
RAM$0.75 per 0.25 GB / 30 daysMemory allocated to your services
Disk Space$0.05 per 0.5 GB / 30 daysStorage space for your applications and data
+ +:::note Daily Spending Control +You can set a daily spending limit in the GUI for your project to keep an eye on costs and avoid unexpected charges. This provides an alternative to configuring automatic resource scaling ranges while keeping your services running optimally. + +Reaching the limit does not stop your project - your services keep running. When a project reaches its daily spending limit, Zerops sends you a warning notification (e-mail) so you can decide whether to raise the limit. The limit resets at midnight (UTC). +::: + +## Additional Services + +Enhance your deployment with these optional services to meet specific requirements for networking, storage, and data transfer. + + + + + + + + + + + + + + + + + + + + + +
ServicePriceDescription
Dedicated IPv4$3.00 per monthExclusive IPv4 address for your project (instead of shared), [billed as a monthly subscription](/billing/overview#dedicated-ipv4-address)
Object Storage$0.02 per GB / 30 daysScalable storage for files, backups, and static assets
+ +## Overage Costs + +When you exceed the resources included in your project core plan, the following charges apply: + + + + + + + + + + + + + + + + + + + + + + + + + + +
ItemPriceDescription
Extra Egress$0.02 per GBData transfer out of your project beyond plan limits
Extra Backup Space$0.50 per 5 GBAdditional storage for automatic, encrypted backups
Extra Build Time$0.50 per 15 hoursAdditional time for building and deploying applications
+ +## Pricing Calculator + +Use our pricing calculator to estimate your monthly costs based on your specific needs: + + +---------------------------------------- + +# Billing > Overview + + +Zerops is prepaid. You top up credit, and Zerops charges your projects, services and add-ons from it. You can add funds manually or automatically, track all your transactions, and download invoices for your records. + +This page explains how charges and subscriptions work, what happens when your credit runs out, and how to manage top-ups and invoices. For the prices themselves, see [Pricing](/billing/pricing). + +## Credit + +Your organization has two balances, both shown in **Credit & Spend Overview** in the Organization section of the main menu: + +- **Credit** - the money you top up, manually or [automatically](#automatic-top-ups). +- **Promo credit** - credit granted by Zerops, for example on sign-up. Every [refund](#subscriptions) is paid out as promo credit too. + +Every charge takes promo credit first, then credit. + +Resource usage (CPU, RAM, disk and overages) is billed by the minute and deducted from your credit hourly. [Subscriptions](#subscriptions) are charged a month in advance. + +Your credit can drop below zero, because a subscription renewal always goes through. Your next top-up pays off the negative balance. + +## Subscriptions + +The [project core](#project-core) and a [dedicated IPv4 address](#dedicated-ipv4-address) are monthly subscriptions: + +- A period starts the moment the subscription is created and lasts one month. Periods don't follow calendar months: a subscription created on 14 March at 10:00 renews on 14 April at 10:00. +- At each renewal, Zerops charges the next month in advance. The renewal goes through even if it takes your credit below zero. +- You get a notification about every renewal. +- Every refund is paid out as promo credit, whether the period was paid with credit or promo credit. + +### Project Core + +Every project has a core subscription, either Lightweight or Serious. See [project core options](/features/infrastructure#project-core-options) for what each includes and [Pricing](/billing/pricing#project-core-plans) for the prices. + +- Creating a project charges the first month of its core. Zerops refuses to create the project if your balance (credit + promo credit) would not stay above zero after that charge. +- The core is charged for as long as the project exists, a stopped project included. +- [Upgrading the core](/features/infrastructure#project-core-upgrade) ends the current core subscription and refunds its unused rest pro rata as promo credit. The new core subscription starts at that moment, and its first month is charged. +- Deleting a project ends its core subscription and refunds the unused rest pro rata as promo credit. + +### Dedicated IPv4 Address + +A dedicated IPv4 address is a project add-on, called **unique IPv4 address** in the GUI. See [Public Access Configuration](/references/networking/public-access#ipv4-configuration) for what it is for and [Pricing](/billing/pricing#additional-services) for the price. A project can have one dedicated IPv4 address. + +#### Activate + +You can activate a dedicated IPv4 address when: + +- the project is active or is being created, +- your organization has made at least one top-up, and +- your balance covers the first month, unless you [reuse a paid period](#reuse-a-paid-period). + +Activate it in the project's IP access settings or in the **Add-ons** section of the project. The GUI shows the price per month and the dates of the first period. The first month is charged right away, and the subscription then renews every month. The fee is never refunded. + +#### Release + +A dedicated IPv4 address is released when: + +- you click **Release IPv4 address** in the **Add-ons** section of the project, +- you delete the project, or +- Zerops [stops the project](#when-credit-runs-out). + +The address is removed from the project right away, and the project falls back to the shared IPv4. The paid period stays with your organization until it ends. + +#### Reuse a Paid Period + +If you activate a dedicated IPv4 address on any project of your organization before a released period ends, Zerops reuses that period at no extra charge. The GUI shows this as **Reuse paid IPv4 address**. The period keeps its end date, and the next renewal is charged as usual. + +The project gets an address that may differ from the released one, so check the DNS A records of your domains. A period that you don't reuse expires at its end, and nothing more is charged for it. + +## When Credit Runs Out + +Zerops may stop the projects of an organization that has run out of credit. When Zerops stops a project: + +- its services stop, +- its dedicated IPv4 address is [released](#release), and +- its core is still charged, because the project still exists. + +A stopped project stays stopped after a top-up. Start it with **Start project** on the project in the GUI, or with `PUT /project/{id}/start` in the [public API](/references/api). Zerops starts the project only if your balance (credit + promo credit) is above zero. If it isn't, the GUI asks you to top up credit first. + +Starting the project doesn't bring back its dedicated IPv4 address. Activate it again: while the released period lasts, it is [reused at no extra charge](#reuse-a-paid-period). + +Enable [automatic top-ups](#automatic-top-ups) to keep your credit above zero. + +## Manual Top-up + +Manual top-ups give you direct control over your account funding. To add credits to your account immediately: + +1. Navigate to **Credit & Spend Overview** in the Organization section of the main menu +2. Click on **Top up credit** and fill in the [billing information](#billing-information) +3. Enter your desired top-up amount (minimum $10 VAT excl.) +3. Complete payment using your saved or new payment method + +## Automatic Top-ups + +Automatic top-up ensures your projects continue running without interruption by replenishing your credits when they run low. + +:::note Prerequisites +Automatic top-ups are available once you have made at least one manual top-up, saved a payment method, and provided your [billing information](#billing-information). The saved card is charged off-session, so a valid payment method must stay on file. +::: + +To turn them on, navigate to **Credit & Spend Overview** in the Organization section of the main menu, open the automatic top-up settings, and configure the three values described below. + +### How Automatic Top-ups Work + +When enabled, Zerops periodically checks your balance and tops it up by a fixed amount whenever your credit drops below a threshold you choose, up to a limit you set for each calendar month. +Zerops initiates an automatic payment when: + +- Your combined balance (credit + promo credit) drops **below your threshold** +- You have automatic top-ups enabled +- The top-up wouldn't exceed your **calendar-month limit** + +:::note Important notes +- Each top-up charges the **fixed amount** you configured, regardless of how fast you're spending +- Your balance is checked periodically (every few minutes), so a top-up can take a few minutes to appear after you drop below the threshold +- The final automatic top-up of the month is reduced so the month's total lands exactly on your calendar-month limit; after the limit is reached, automatic top-ups pause until the next calendar month +- To avoid repeatedly hitting your payment method (which can get a card flagged or blocked by the payment processor), top-ups are spaced out: after a **successful** top-up Zerops waits **1 hour** before the next one, and after a **failed** top-up it waits **1 day** before trying again +- If a charge fails, Zerops notifies you so you can check the validity and available funds of your saved card. After **3 failed attempts in a row**, automatic top-up is turned off and you're notified by email; re-enable it once your payment method is working again +- Auto top-up limits don't affect manual payments — add any amount manually regardless of automatic settings +::: + +### Configuration Options + +#### Threshold +When your combined balance (credit + promo credit) drops below this value, an automatic top-up is triggered. + +#### Top-up Amount +The fixed amount charged to your saved card on each automatic top-up. + +- Minimum: $10 (matches the minimum manual payment) +- Maximum: $10,000 per top-up + +#### Calendar-Month Limit +The maximum total that can be automatically charged within a single calendar month (UTC). This safeguards against unexpected costs: once the limit is reached, automatic top-ups pause until the next calendar month. + +- Must be at least the top-up amount (so at least one top-up can go through each month) + +#### Real-World Example + +**Scenario:** Application with ~$50 weekly operating costs and an initial manual top-up of $100 + +**Your Settings:** +- Threshold = $50 +- Top-up amount = $200 +- Calendar-month limit = $500 + +**Expected behavior:** +- When your balance falls below $50, Zerops charges $200 to bring it back up +- Each top-up is exactly $200, no matter how fast you're spending, until you approach the calendar-month limit +- After two top-ups ($400), a full $200 would exceed the $500 limit, so the next top-up is reduced to $100, bringing the month's total to exactly $500 +- Automatic top-ups then pause until the limit resets at the start of the next calendar month (UTC) + +## Billing Information + +You are required to enter billing details for all transactions (manual and automatic top-ups), with one exception: + +- EU-based users who are not VAT payers with transactions under $350 + +You can save your billing details by navigating to **Invoices & Billing Settings** in the Organization section of the main menu. + +## Invoices + +Zerops provides easy access to all invoices generated for manual and automatic top-ups within your organization. + +To view and manage your invoices navigate to **Invoices & Billing Settings** in the Organization section of the main menu. + +## Export Credit Consumption Records + +Zerops allows you to download monthly reports of your credit consumption history for analysis and record-keeping. + +1. Navigate to **Credit & Spend Overview** in the Organization section +2. Find the **Export Credit Consumption Records** section +3. Click on any month button to download that period's report + +Reports are available for the past 12 months in TXT format and include: +- Client information and reporting period +- Starting and ending balances +- Itemized resource charges by project and service +- Credit transactions (top-ups, refunds, promotional credits) +- Clear distinction between common (paid) and promotional credits + ---------------------------------------- # Alpine > Overview @@ -47423,7 +47480,7 @@ Build containers start with minimum resources and scale vertically up to maximum The time limit for the whole build pipeline is **1 hour**. After 1 hour, Zerops will terminate the build pipeline and delete the build container. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ## Troubleshooting builds diff --git a/apps/docs/static/llms-small.txt b/apps/docs/static/llms-small.txt index 820906f2..d5b86089 100644 --- a/apps/docs/static/llms-small.txt +++ b/apps/docs/static/llms-small.txt @@ -3839,12 +3839,12 @@ A **connector** is a ready-made provider login (Claude Code, GitHub, OpenAI Code # Zbox > Pricing -Zerops Box has no price of its own. You pay for the Box Workspace service like for any other Zerops service, at the rates on the [Zerops pricing](/company/pricing) page. +Zerops Box has no price of its own. You pay for the Box Workspace service like for any other Zerops service, at the rates on the [Zerops pricing](/billing/pricing) page. ## What you pay for - **The workspace VM's resources.** A workspace has fixed resources and never autoscales, so you pay for the CPU cores, RAM and disk you [set](/zbox/workspace-service#resizing), whether sandboxes use them or not. CPU is billed at the shared or dedicated rate, depending on the CPU mode, shared unless you choose dedicated. -- **The project.** The project core, and optional extras such as a dedicated IPv4 address or egress over the included amount, are billed per project as usual ([pricing](/company/pricing), [top-up and billing](/company/payment)). +- **The project.** The project core, and optional extras such as a dedicated IPv4 address or egress over the included amount, are billed per project as usual ([pricing](/billing/pricing), [billing](/billing/overview)). ## What costs nothing extra @@ -6247,7 +6247,7 @@ Build containers start with minimum resources and scale vertically up to maximum The time limit for the whole build pipeline is **1 hour**. After 1 hour, Zerops will terminate the build pipeline and delete the build container. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ## Troubleshooting builds @@ -14523,7 +14523,7 @@ You can configure scaling settings: ### Basic settings -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your PostgreSQL service: @@ -21040,7 +21040,7 @@ You can configure scaling settings: ### Basic settings -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your MariaDB service: @@ -22499,7 +22499,7 @@ You can configure scaling settings: ### Basic settings -**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](https://zerops.io/#pricing) for costs. +**CPU Mode**: Choose between shared (cost-effective, variable performance) or dedicated (consistent performance, higher cost). You can change CPU mode once per hour. See [pricing](/billing/pricing#resource-pricing) for costs. **Resource limits**: Configure minimum and maximum resources for your KeyDB service: @@ -25290,7 +25290,7 @@ Zerops offers three public access methods: zerops.app subdomains (dev only, 50MB - Configurable firewall: blacklist or whitelist per port ## Gotchas -1. **Dedicated IPv4 is non-refundable**: $3/month, auto-renews — the fee isn't refunded if removed early, but the address can be reused in another project until the subscription ends. If a renewal fails for lack of credit, the address is released and must be added again after a top-up +1. **Dedicated IPv4 is a monthly subscription, never refunded**: $3 per month. Releasing it frees the address right away, and a new activation may get a different address, so update the DNS A records. Activation, release and reuse of a paid period: [Billing](/billing/overview#dedicated-ipv4-address) ---------------------------------------- @@ -25794,7 +25794,7 @@ Work through these steps **in order**: | Feature | Shared IPv4 | Dedicated IPv4 | |---------|-------------|----------------| -| Cost | Free | $3 / 30 days | +| Cost | Free | $3 per month ([billing](/billing/overview#dedicated-ipv4-address)) | | Protocol support | HTTP/HTTPS only | All (TCP/UDP/HTTP) | | Connections | Limited, shorter timeouts | Full capacity | | Blacklist risk | Shared with other users | Isolated | @@ -26965,12 +26965,8 @@ MariaDB, PostgreSQL, Qdrant, NATS, Meilisearch, Local Storage, SeaweedFS. - **Protected tags**: Exempt from automatic deletion — use for critical snapshots ## Storage Limits -| Plan | Backup Storage | Egress | -|------|---------------|--------| -| Lightweight | 5 GB | 100 GB | -| Serious | 25 GB | 3 TB | -| Technical max | 1 TiB per project (shared across all services) | -| Technical max | 1 TiB per project (shared across all services) | +- Included backup storage and egress depend on the project core: [pricing](/billing/pricing#project-core-plans) +- Technical max: 1 TiB per project (shared across all services) ## Retention Defaults - Minimum kept: 7 daily + 4 weekly + 3 monthly @@ -29964,7 +29960,7 @@ Dedicated CPU gives exclusive access to a full physical CPU core(s), ensuring co CPU mode can be changed (once per hour) as needed. ::: -See the [pricing](/company/pricing#resource-pricing) for the difference between CPU modes. +See the [pricing](/billing/pricing#resource-pricing) for the difference between CPU modes. #### Minimum and Maximum CPU Cores @@ -30879,7 +30875,7 @@ All runtime services use the same hardware resources for build containers: Build containers start with minimum resources and scale vertically up to maximum capacity as needed. :::info -Build container resources are not charged. Build costs are covered by the standard Zerops [project fee](https://zerops.io/#pricing). +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ### Build time limit @@ -31354,7 +31350,7 @@ Production applications, high-traffic websites, mission-critical business applic -For detailed pricing information on both core types, visit our [pricing page](/company/pricing#project-core-plans). +For detailed pricing information on both core types, visit our [pricing page](/billing/pricing#project-core-plans). #### Project Core Upgrade @@ -31367,7 +31363,7 @@ The core upgrade is a **partially destructive process** that will temporarily di **What happens during upgrade:** - All project logs and statistics will be lost (forwarded logs/statistics are not affected) - Services will be network-unavailable during the process (avg. 35 seconds but can take longer) -- $10 project core fee will be charged upon upgrade +- The unused rest of the current core is refunded as promo credit, and the first month of Serious Core is charged (see [Billing](/billing/overview#project-core)) - Free project resources will reset to Serious Core limits - Project IP addresses remain unchanged @@ -33112,10 +33108,7 @@ Each Zerops project has a **technical maximum backup storage limit of 1 TiB**: - This quota is shared across all service backups within the project ### Billing -- **Lightweight Project Core**: 5 GB backup storage and 100 GB egress included -- **Serious Project Core**: 25 GB backup storage and 3 TB egress included - -When you exceed your plan's free limits, **additional charges apply** according to our [pricing](/company/pricing#overage-costs). +Each [project core plan](/billing/pricing#project-core-plans) includes some backup storage and egress. When you exceed your plan's free limits, **additional charges apply** according to our [pricing](/billing/pricing#overage-costs). ### Retention Policy and Configuration @@ -33223,7 +33216,7 @@ When a project is deleted, the encryption key is permanently destroyed after 7 d 1. **Review & Prune**: Delete unnecessary manual backups or remove protected status from older backups 2. **Adjust Retention Policy**: Reduce minimum retention counts if your recovery requirements allow 3. **Optimize Schedule**: Reduce backup frequency if daily backups aren't essential -4. **Monitor Costs**: Check usage against your free tier (5GB/25GB) to avoid unexpected overage charges +4. **Monitor Costs**: Check usage against the backup storage included in your [project core plan](/billing/pricing#project-core-plans) to avoid unexpected overage charges 5. **Contact Support**: If you need assistance managing storage ### Backup Failures @@ -37218,7 +37211,7 @@ All runtime services use the same hardware resources for build containers: Build containers start with minimum resources and scale vertically up to maximum capacity as needed. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ### Build time limit @@ -40408,7 +40401,7 @@ Build containers start with minimum resources and scale vertically up to maximum The time limit for the whole build pipeline is **1 hour**. After 1 hour, Zerops will terminate the build pipeline and delete the build container. :::info -Build container resources are not charged separately. Limited build time is included in your [project core plan](/company/pricing#project-core-plans), with additional build time available if needed. +Build container resources are not charged separately. Limited build time is included in your [project core plan](/billing/pricing#project-core-plans), with additional build time available if needed. ::: ## Troubleshooting builds diff --git a/apps/docs/static/llms.txt b/apps/docs/static/llms.txt index 66803f03..6b1d6ecf 100644 --- a/apps/docs/static/llms.txt +++ b/apps/docs/static/llms.txt @@ -5,7 +5,7 @@ ## Docs - [Full Docs](https://docs.zerops.io/llms-full.txt): The complete documentation as a single file (362 pages, no images). -- [Core Docs](https://docs.zerops.io/llms-small.txt): The same, trimmed to the core platform — excludes API/CLI references, company and help pages. +- [Core Docs](https://docs.zerops.io/llms-small.txt): The same, trimmed to the core platform — excludes API/CLI references, company, pricing and billing, and help pages. Every page below is also reachable in its rendered form by dropping the `.md` suffix, and any docs.zerops.io URL can be turned into clean markdown by adding it. @@ -343,8 +343,6 @@ suffix, and any docs.zerops.io URL can be turned into clean markdown by adding i - [Deno > How To > Controls](https://docs.zerops.io/deno/how-to/controls.md) - [Deno > How To > Build Process](https://docs.zerops.io/deno/how-to/build-process.md) - [Deno > How To > Build Pipeline](https://docs.zerops.io/deno/how-to/build-pipeline.md) -- [Company > Pricing](https://docs.zerops.io/company/pricing.md) -- [Company > Payment](https://docs.zerops.io/company/payment.md) - [Company > Branding](https://docs.zerops.io/company/branding.md) - [Company > About](https://docs.zerops.io/company/about.md) - [Clickhouse > Overview](https://docs.zerops.io/clickhouse/overview.md) @@ -361,6 +359,8 @@ suffix, and any docs.zerops.io URL can be turned into clean markdown by adding i - [Bun > How To > Controls](https://docs.zerops.io/bun/how-to/controls.md) - [Bun > How To > Build Process](https://docs.zerops.io/bun/how-to/build-process.md) - [Bun > How To > Build Pipeline](https://docs.zerops.io/bun/how-to/build-pipeline.md) +- [Billing > Pricing](https://docs.zerops.io/billing/pricing.md) +- [Billing > Overview](https://docs.zerops.io/billing/overview.md) - [Alpine > Overview](https://docs.zerops.io/alpine/overview.md) - [Alpine > How To > Upgrade](https://docs.zerops.io/alpine/how-to/upgrade.md) - [Alpine > How To > Trigger Pipeline](https://docs.zerops.io/alpine/how-to/trigger-pipeline.md) diff --git a/zerops-llm-script.ts b/zerops-llm-script.ts index e804c15c..fe03ff0f 100644 --- a/zerops-llm-script.ts +++ b/zerops-llm-script.ts @@ -198,7 +198,7 @@ async function generateLLMDocs() { '## Docs', '', `- [Full Docs](https://docs.zerops.io/llms-full.txt): The complete documentation as a single file (${optionalFiles.length} pages, no images).`, - '- [Core Docs](https://docs.zerops.io/llms-small.txt): The same, trimmed to the core platform — excludes API/CLI references, company and help pages.', + '- [Core Docs](https://docs.zerops.io/llms-small.txt): The same, trimmed to the core platform — excludes API/CLI references, company, pricing and billing, and help pages.', '', 'Every page below is also reachable in its rendered form by dropping the `.md`', 'suffix, and any docs.zerops.io URL can be turned into clean markdown by adding it.', @@ -226,7 +226,7 @@ async function generateLLMDocs() { const outputTinyFile = path.resolve(publicDir, 'llms-small.txt') - const tinyExclude = ['references', 'company', 'help'] + const tinyExclude = ['references', 'company', 'billing/', 'help'] const tinyFiles = files.filter((filename: string) => !tinyExclude.some(exclude => filename.includes(exclude))) const tinyContent = await generateContent( diff --git a/zerops.yml b/zerops.yml index 103155a3..0d26648a 100644 --- a/zerops.yml +++ b/zerops.yml @@ -45,6 +45,34 @@ zerops: true - sudo service nginx reload routing: + redirects: + - from: /company/payment + to: /billing/overview + status: 301 + - from: /company/payment/ + to: /billing/overview + status: 301 + - from: /company/payment.md + to: /billing/overview.md + status: 301 + - from: /company/billing + to: /billing/overview + status: 301 + - from: /company/billing/ + to: /billing/overview + status: 301 + - from: /company/billing.md + to: /billing/overview.md + status: 301 + - from: /company/pricing + to: /billing/pricing + status: 301 + - from: /company/pricing/ + to: /billing/pricing + status: 301 + - from: /company/pricing.md + to: /billing/pricing.md + status: 301 headers: - for: "~* \\.md$*" values: