diff --git a/apps/docs/docusaurus.config.js b/apps/docs/docusaurus.config.js index 73abfdc0..d660a3da 100644 --- a/apps/docs/docusaurus.config.js +++ b/apps/docs/docusaurus.config.js @@ -34,6 +34,28 @@ const config = { crossorigin: "anonymous", }, }, + // Agent/LLM discovery. There is no formal relation for llms.txt -- + // the convention is the well-known /llms.txt path -- but advertising it in + // costs nothing and is picked up by some crawlers and dev tools. + // Per-page markdown alternates are emitted by src/theme/DocItem/Layout. + { + tagName: "link", + attributes: { + rel: "alternate", + type: "text/plain", + href: "https://docs.zerops.io/llms.txt", + title: "llms.txt", + }, + }, + { + tagName: "link", + attributes: { + rel: "alternate", + type: "text/plain", + href: "https://docs.zerops.io/llms-full.txt", + title: "llms-full.txt", + }, + }, ], plugins: [ './src/plugins/markdown-source', diff --git a/apps/docs/static/llms-full.txt b/apps/docs/static/llms-full.txt index b6be83cc..907b0080 100644 --- a/apps/docs/static/llms-full.txt +++ b/apps/docs/static/llms-full.txt @@ -3256,54 +3256,62 @@ Manual top-ups give you direct control over your account funding. To add credits ## Automatic Top-ups -:::caution Beta version -Available only for customers who have previously made a manual top-up, have a saved payment method, and have provided billing information. +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. ::: -Automatic top-up ensures your projects continue running without interruption by replenishing your credits when they run low. +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 monitors your credit balance and consumption rate to determine when and how much to top up, always respecting your configured limits. +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 remaining credits are sufficient for **less than 10 days** of operation at your **current consumption rate** +- Your combined balance (credit + promo credit) drops **below your threshold** - You have automatic top-ups enabled -- Your [settings](#billing-information) allow for the payment amount +- The top-up wouldn't exceed your **calendar-month limit** :::note Important notes -- The charge amount is estimated based on your actual usage patterns, not maximum possible amounts -- Negative balances are included in the next auto top-up (within your maximum charge limit) -- The system checks your balance immediately after enabling auto top-ups, potentially triggering an immediate payment +- 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 -#### Period -The timeframe for which the maximum configured auto-charge amount is checked. Can be set to either: +#### Threshold +When your combined balance (credit + promo credit) drops below this value, an automatic top-up is triggered. -- **Weekly**: Maximum charge amount applies to a 7-day rolling window -- **Monthly**: Maximum charge amount applies to a 30-day rolling window +#### Top-up Amount +The fixed amount charged to your saved card on each automatic top-up. -#### Maximum Charge Amount -The maximum amount that can be auto-charged in the given period. This serves as a safeguard against unexpected costs due to traffic spikes or other unforeseen circumstances. +- Minimum: $10 (matches the minimum manual payment) +- Maximum: $10,000 per top-up -- Minimum setting: $10 (matches the minimum manual payment) +#### 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 $20 weekly operating costs and initial manual top-up of $100 +**Scenario:** Application with ~$50 weekly operating costs and an initial manual top-up of $100 **Your Settings:** -- Period = Weekly -- Maximum charge amount = $150 +- Threshold = $50 +- Top-up amount = $200 +- Calendar-month limit = $500 **Expected behavior:** -- System adds approximately $20-30 when less than 10 days of credits remain (around day 35) -- Payments continue in small increments aligned with your usage patterns -- During traffic spikes, payments adjust to match higher consumption (up to $150 weekly limit) -- Payment amounts return to normal when usage decreases +- 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 @@ -3410,7 +3418,9 @@ Services in Zerops require computing resources that are billed separately from y :::note Daily Spending Control -You can set daily spending limits in GUI for your project to control costs and avoid unexpected charges. This provides an alternative to configuring automatic resource scaling ranges while keeping your services running optimally. +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 @@ -8490,7 +8500,7 @@ Zerops provides an automated, secure backup system for supported services. This ## Supported Services -Zerops provides automated backup functionality for the following services. For specific backup format details and restore instructions, visit each service's documentation: [MariaDB](/mariadb/how-to/backup), [PostgreSQL](/postgresql/how-to/backup), [Qdrant](/qdrant/overview), [Elasticsearch](/elasticsearch/overview), [NATS](/nats/overview), [Meilisearch](/meilisearch/overview), and [Shared Storage](/shared-storage/how-to/backup). +Zerops provides automated backup functionality for the following services. For specific backup format details and restore instructions, visit each service's documentation: [MariaDB](/mariadb/how-to/backup), [PostgreSQL](/postgresql/how-to/manage#backups), [Qdrant](/qdrant/overview), [Elasticsearch](/elasticsearch/overview), [NATS](/nats/overview), [Meilisearch](/meilisearch/overview), and [Shared Storage](/shared-storage/how-to/manage#backups). ## Managing Backups in the UI @@ -9313,6 +9323,20 @@ Remember that only publicly accessible objects will be cached by the CDN. Privat Zerops was built on the idea of **environment parity** — giving developers the full development lifecycle, from remote development to highly available production, with the observability and developer tools for maximum flexibility, and sensible defaults so the configs stay reasonable. Turns out that's **exactly what coding agents need** to produce and iterate on production-ready applications. +
+