---
title: "Pricing and limits"
description: "Plurabase has no published prices and charges nothing during its private pilot. What the pilot's limits are and what happens when one is reached."
slug: "pricing"
locale: "en"
group: "start"
order: 4
last_reviewed: 2026-10-26
---

# Pricing and limits

> Status: In development (billing.plans)

Plurabase has no published prices and no paid plans. Nothing is charged during the private pilot. Billing code for Stripe's test mode (checkout, invoices, and what happens when a payment fails) exists, but no host runs it and no prices are set in it. Usage metering exists as code too: it measures each project's database, Storage, Sites and build time per month and applies per-organization plan limits, but no host runs it, so the limits below are the only ones in force. A first paid offer is milestone M3 on the delivery plan; prices will be set only after the cost of running projects, Sites, builds and backups has been measured. There is no date.

## Limits in the pilot

- One project fits on the pilot host. A project runs in a 2 vCPU, 3 GiB memory slice with a 4 GiB data volume.
- Each Site accepts a ZIP up to 4 MiB that expands to at most 16 MiB.
- Each Site accepts two uploads in its lifetime, including failed ones, and keeps two releases.
- Agent tokens are valid for 24 hours or 7 days.

## When a limit is reached

- **Project capacity:** creating a project is refused when the host has no room. No other project is affected.
- **Data volume:** when the 4 GiB volume is full, writes fail. The volume does not grow and nothing is billed.
- **Site size or uploads:** an upload over the limit is rejected before it is published; the current release keeps serving.

These limits belong to the pilot and will change before any paid offer. The [facts page](/docs/facts/) keeps the current values.