TimeWitness

What it costs

Per organisation, per month. What a plan changes is how much of this app you use, never how narrow a bound is and never whether something already issued still checks out.

Paying for a plan

  • Pro and Team are paid for by card, in a checkout Stripe runs. The owner of an organisation starts it from that organisation's page, with a passkey.
  • The plan is changed or cancelled in the same place, and the organisation's page says where it stands and what happens next.
  • An organisation on Pro moves up to Team from its page. Team is paid for at its own checkout, Pro stops once Team is paid, and the Pro time already paid for and not used is credited against the next invoice. The credit is not paid out as money.
  • The free tier is what every organisation starts on, and it is not a subscription. It does not lapse.

Free

Free

  • Up to five machines, each one a key enrolled to the organisation and not retired, whether its repositories are public or private.
  • The same bound and the same evidence as any paid plan.
  • An organisation, the colleagues you invite to it, and everything it holds exported or deleted whenever you choose.
  • Checking is free for everybody and always will be, with no account and no call to us.

Pro

USD 15 a month, for one person

  • Everything on the free tier, without the limit of five machines.

Team

USD 49 a month, for an organisation

  • Everything on Pro, for everybody in the organisation.

The same for everybody, paid or not

  • Full precision on every plan, paid or free. A coarser interval is never sold to somebody who has not paid, and a plan differs only in how much of this app it carries.
  • Nothing is ever priced per receipt, per check or per countersign. A price on each of those makes people ration them, and the point is one on every event rather than on the ones somebody decided were worth paying for.
  • Checking costs nothing, needs no account and reaches nothing of ours. That is true today and it stays true, and the build of the agent fails if checking ever starts to need us.
  • The GitHub Action stamps any repository, public or private, and the verifier checks any receipt, both free with no limit and with no account. The limit of five machines counts only keys an organisation enrols in this app.

What happens if the money stops

Four states, and the app records them. Nothing outside it is prevented.

  • Active, on a payment goes through: everything the plan carries.
  • Past due, on a payment fails: everything, with a notice, for fourteen days while the provider retries.
  • Lapsed, on the retries run out, or somebody cancels: sign in and export, on the free tier.
  • Closed, on ninety days after the lapse at the earliest, and a week after the second of two emails at the earliest: sign in and export, and the copies of its receipts held here are deleted.

What a lapse does not do

  • Nothing already issued stops being checkable. Every receipt this organisation ever made still verifies offline, in every state on this page, closed included, and checking one needs no account, no payment and nothing of ours.
  • No key log entry is ever removed, in any state.
  • Nothing outside this app is prevented. An agent goes on stamping and two machines go on countersigning each other, with no call to us in either, whatever this page says. What a lapse changes is what this app does next: it issues certificates for keys up to the free tier, and none once closed. This app records what was paid, and recording is not stopping.
  • An export is never refused, in any state. Everything this app holds for this organisation comes out as one file, and that stays true while the notice period runs out.
  • No state here touches a bound, a reading or a width. What is paid for is how much this app will do next, never how narrow anything is: the bound is the same for everybody.
  • No page of this app has legal weight, and no regulation we have read asks for any of this.