Skip to content
Facteur

One inbox's quota should never depend on another's

Each inbox can have its own ceiling of messages per day and per month, from the Solo plan. A test suite that runs away stops at its limit, without draining the volume of the rest of the team.

Today's quotas 4 inboxes · example
  • ci-nightly 4,120 / 5,000
  • e2e-signature 7,640 / 8,000

    90 % alert sent

  • recette-manuelle 240 / 2,000
  • load-test 3,000 / 3,000

    ceiling reached, messages refused

infra/quotas.ts TypeScript
// Ceilings are set through the API, so from your infrastructure code.
await fetch('https://api.facteur.eu/inboxes/j3k9x2mq', {
  method: 'PATCH',
  headers: {
    authorization: 'Bearer ' + process.env.FACTEUR_API_KEY, // a key that writes
    'content-type': 'application/merge-patch+json',
  },
  body: JSON.stringify({
    quota: {
      daily: 5000,     // an infinite loop stops here
      monthly: 80000,  // the budget of the month
      // 'reject': later messages are refused, with a code.
      // 'alert':  we warn you, and let them through.
      onExceed: 'reject',
    },
  }),
});
The figures in the panel are an example. The code is a real call: null removes a ceiling.

What you can set

01

From the first paid plan

Solo

Capping an inbox is not kept for a top plan. It is the minimum for a team to share an account without getting in each other's way, so it is included from the Solo plan. The Free plan does not have it.

02

Daily and monthly limits

Both, independently, per inbox. The daily limit stops an infinite loop; the monthly one protects the budget. The monthly ceiling can also be a share of the plan's volume, and a workspace can have its own.

03

You choose the behaviour

reject | alert

At the ceiling, the inbox refuses the next messages. Each one leaves a trace with the code INBOX_QUOTA_EXCEEDED, which your test reads through the API: it fails for the right reason. Or the inbox keeps accepting and only warns you. Whether it serves CI or a customer demo, the right choice differs.

04

Alerts before the wall

80 · 100 %

With no setting, owners and administrators are told at 80 % and then at 100 % of the period's volume. You can add up to four thresholds of your own. An alert leaves once per threshold crossed and per period, never twice.

05

Told where you read

Up to three destinations per alert rule, on top of the administrators: an email address on every plan, and from Solo up a Slack or Discord channel, a PagerDuty or OpsGenie service. The alert carries the figure, the organisation, the workspace or the inbox it concerns, and a link to the usage screen. For PagerDuty and OpsGenie, Facteur opens the incident and never closes it: whoever is on call does.

06

Usage per inbox

The usage screen answers "who used my quota", not just "how much". It gives what each inbox received and refused over the period, and the organisation's usage day by day.

07

Told before it runs out

When the pace of the last days would use up the volume before the end of the period, an alert says so, with the expected day. Another one leaves when attachments take 80 % of the included storage.

08

Spending cap

An amount beyond which overage stops: the next messages are refused until the next period. A surprise bill is a design defect, not a fact of life.

09

Ceilings driven by the API

PATCH /inboxes/{inboxId}

The daily ceiling, the monthly one and the behaviour at the ceiling are set with an API key. Your quotas live in your repository, not in the memory of whoever last clicked. Who receives the alerts is set in the application, and only there: a stolen key cannot silence the alerts of an account.

Three ways out, and you pick

Going past your volume is a normal event in a project's life. It should not be an incident.

01
Option 1

A pack, right away

A pack adds operations to those of the plan, without touching the subscription. Card payment is not in service yet: until it is, you buy a pack by writing to support from the application.

02
Option 2

Overage takes over

Nothing to do, nothing breaks. On a paid plan, the extra messages are billed at the end of the period, within your spending cap.

03
Option 3

We refuse, cleanly

An explicit refusal rather than a message swallowed in silence. The refused message leaves a trace with its code, in the application and through the API. Your test fails for the right reason, and you see it.

Take back control of your capacity

Per-inbox ceilings, alerts before the limit and a spending cap: included from the Solo plan, with no sales conversation.