tikinang · Oct 27, 2026 · Oct 27, 2026
diff --git 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 <Var name="serviceDisplay" /> builds

diff --git a/apps/docs/content/company/payment.mdx → apps/docs/content/billing/overview.mdx b/apps/docs/content/company/payment.mdx → 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
 </DropdownItem>
 </Dropdown>
 
-## 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 → apps/docs/content/billing/pricing.mdx b/apps/docs/content/company/pricing.mdx → 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
     <tr>
       <td className="w-fit whitespace-nowrap"><strong>Dedicated IPv4</strong></td>
       <td className="w-fit whitespace-nowrap"><strong>$3.00</strong> per month</td>
-      <td className="w-fit">Exclusive IPv4 address for your project (instead of shared)</td>
+      <td className="w-fit">Exclusive IPv4 address for your project (instead of shared), <a href="/billing/overview#dedicated-ipv4-address">billed as a monthly subscription</a></td>
     </tr>
     <tr>
       <td className="w-fit whitespace-nowrap"><strong>Object Storage</strong></td>
-      <td className="w-fit whitespace-nowrap"><strong>$0.01</strong> per GB / 30 days</td>
+      <td className="w-fit whitespace-nowrap"><strong>$0.02</strong> per GB / 30 days</td>
       <td className="w-fit">Scalable storage for files, backups, and static assets</td>
     </tr>
   </tbody>

diff --git 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
@@ -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
@@ -126,7 +126,7 @@ Production applications, high-traffic websites, mission-critical business applic
   </tbody>
 </table>
 
-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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -17,7 +17,7 @@ Get quick answers to your related questions about Zerops from frequently asked q
   </FAQItem>
   <FAQItem 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 <a href="/company/pricing">pricing page</a> to explore the options that best suit your needs.
+    recommend visiting our <a href="/billing/pricing">pricing page</a> 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.
   </FAQItem>

diff --git 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:
   />
 </figure>
 
-**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
@@ -35,7 +35,7 @@ You can configure scaling settings:
   />
 </figure>
 
-**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
@@ -278,7 +278,7 @@ You can configure scaling settings:
   />
 </figure>
 
-**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
@@ -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