Billing and plans

Overview

The Overview tab sums up the organization's current subscription: the plan, its status (trialing, active, past due…), the price and billing interval, the current period and the renewal date, or the cancellation date if a stop is already scheduled.

The Manage in Stripe button opens the customer portal to update the card or fetch receipts. It shows up neither during the trial nor on the Free plan, where there is nothing to manage.

The 14-day trial

Every paid subscription starts with a 14-day trial, once per organization. A card is asked for when you subscribe, but nothing is charged during the trial: the first payment goes out on day 15, and the subscription carries on by itself.

Cancel before the end of the trial from the Stripe portal and you pay nothing, the organization drops back to Free. Once the trial has ended, converted or been cancelled along the way, a new subscription starts as a paid one, with no second free period.

Changing plan

The Plans tab shows the catalogue (Free, Starter, Pro, Business) with the current plan highlighted, and a monthly or yearly toggle. Prices are shown in the currency matching your organization's country.

Picking a higher plan opens a dialog that computes the proration first: you see the target price, the amount charged right away and the amount of the next invoice before confirming. A lower plan is scheduled for the end of the current period instead; a banner recalls the date and lets you cancel the change while it has not taken effect.

Two optional fields come with a plan change: a promo code, checked immediately and whose discount is displayed before you confirm, and a referral code if someone recommended Pierrr to you.

Add-ons

Add-ons layer optional capacity on top of your plan. They attach and detach from the Overview tab, at the price shown in the catalogue for your plan and your country:

• Pierrr Agent, one licence seat per server you enroll. Stackable, and cheaper as your plan goes up.
• Automatic backups, the scheduling of your project backups. One per organization, included on the Business plan.
• Application slot, one more deployable application per unit bought.
• Database capacity, ten more gigabytes per unit bought on the managed database.
• Persistent volume, bought per project and billed per gigabyte. A volume you buy starts unmounted: open its node in the Topology to attach it to a container and a path.
• Redis instance, a dedicated cache bought at the organization level then linked to one or more projects from the Topology.
• S3-compatible object storage, same model as the cache: bought for the organization, then linked to the projects that need it.

Removing an add-on cuts nothing straight away: the service stays active until the end of the period already paid for, then the cancellation takes effect. The current period is not refunded. An add-on unavailable on your plan is flagged as such in the catalogue.

Attaching a Pierrr Agent licence

If you bought a Pierrr Agent licence outside the console, from the website for instance, the Attach a licence button on the Overview tab ties the code you received by email to your organization. The link is permanent: the seat stays bound to that organization and cannot be detached.

Invoice history

The History tab lists the invoices issued by Stripe: number, amount, currency, status (paid, due…), period covered and payment date. Each row opens the hosted invoice or downloads the PDF, handy for accounting.

Quotas

Each plan comes with explicit quotas (projects, containers per project, instances, domains, security scans…). When you reach a quota, the action offers a move to a higher plan rather than failing silently.

Free plan sleep rules

On the Free plan, projects hosted by Pierrr follow two sleep rules. The free tier runs on shared servers: pausing idle projects, and free projects at night, keeps capacity available for everyone. Projects self-hosted on your own server through the Pierrr agent are not affected, and neither are paid plans (Starter, Pro, Business).

• Nightly sleep: every night from 00:00 to 08:00, Africa/Abidjan time (UTC+0, no daylight saving), the project's containers are stopped at 00:00 and restarted automatically at 08:00. During that window you cannot start, restart, build or deploy the project: these actions come back at 08:00. Visitors of the site see a "site is sleeping" page (HTTP 503).
• Inactivity: a Free project with no deployment and no action from a member of the organization (start, stop, restart, build, deploy) for 30 days is switched off at the next nightly sleep, at 00:00, and does not restart by itself at 08:00. A member wakes it up from the console with the Wake up button, outside the night window. No warning email is sent beforehand.

In both cases nothing is deleted: the managed database, the volumes and the project's files are kept. Moving to a paid plan lifts both rules immediately. Automatic deployment on every push stays reserved for paid plans.

Coming back under the plan limits

An organization moving back to a smaller plan, after a cancellation or an unpaid invoice, can end up above that plan's limits. It then has 7 days to reorganize: a banner at the top of the Billing page announces the deadline and lists the quotas exceeded, and you are warned by email, then reminded the day before.

After that, only the resources beyond the plan are stopped: the oldest ones keep running, and nothing is deleted, not code, not volumes, not databases, not backups. Everything restarts after resubscribing, or after removing the extra resources to fit within the plan.

Failed payment

If the subscription renewal fails, the organization is suspended and the console narrows down to a payment screen, with a button that opens the outstanding invoice. Paying restores access immediately.