The right permission for each person
An analyst investigates without being able to publish, an approver reviews without being able to edit, a client sees their sites and nothing else.
Teams, permissions and multi-organisation
Seven built-in roles and roles of your own, limited to some sites, two-factor authentication, a tamper-evident audit log, and the management of several clients from one console with isolated organisations, quotas and invitations.
Where to find it in the console : Administration menu: Users and access, Audit log, Tenants and MSPs.
What it is for
Better protected accounts
Two-factor authentication through a TOTP app with recovery codes, scoped API tokens, and enterprise sign-in under licence.
Know who did what
Every change is recorded with the author, time, origin and before-and-after, in a hash chain you can verify.
Several clients, one console
One organisation per client, isolated from the others, with its quotas, users and reports. Your clients' sites stay protected whatever you do with their access.
A platform, providers, clients
Organisations form a tree. Everyone sees their own space and what is below it, never a neighbour's.
A tree of organisations
The platform is at the root and stays free. Below it, optional providers, then clients. A user belongs to one organisation.
Roles, per site if needed
A role is given to a person for their whole organisation or for a few sites only.
A reviewed publication
A client's administrator edits their configuration, but going live remains with a platform administrator: a client does not change what runs on shared nodes without review.
Roles and permissions
Free
A permission is written resource:action. The seven built-in roles cannot be edited; you create roles of your own to combine permissions.
- Owner, Administrator, Operator, Security analyst, Change approver, Read-only and Client (managed security service provider).
- A role can be limited to a few sites; an API token can be too, and never exceeds the rights of the person who created it.
- Four-eyes approval: a policy version goes live only after an approver agrees.
- Keep at least two owners: the product refuses to remove the last one.
Sign-in and audit log
FreePro and above
Controls on access, and the trace of every action.
- TOTP with single-use recovery codes; the secret is encrypted at rest. Hardware keys (WebAuthn, FIDO2) are not available.
- Licence required: OIDC and SAML enterprise sign-in, and SCIM provisioning.
- Audit log: who, what, when, from where, with the before and after; filters, free CSV, JSON and NDJSON export, CEF and Syslog under licence.
- Verification recomputes the hash chain and reports the first inconsistency. Secrets are never written to it.
Manage several clients
Pro and above
The first organisation, the default one, is free. Adding clients needs a licence; reactivating, exporting and deleting are never locked.
- The « Add a client » wizard: client, quotas, first user, report brand, isolation test and handover. Nothing is created before the last step.
- Quotas on sites, users and clients; the monthly request volume is measured for your invoicing and never cuts traffic.
- A client selector limits every list to one client; an overview shows each one's protection state.
- Suspending cuts console access, not the protection. Archiving requires an export less than 24 hours old and the organisation's name, then opens a grace period before a possible deletion.
Imposed floor and client brand
Pro and above
What is imposed from above can be tightened below, never relaxed.
- A provider imposes a minimum mode, a minimum paranoia level, maximum thresholds and protection settings; a weaker value already in place is raised without erasing anything.
- Integrations only flow downward: an integration receives the alerts of its organisation and of those below it.
- The client's name, logo and colours appear on its reports and refusal pages next to ToutWAF, never in its place.
- Invitations use a single-use link, valid for 7 days by default: no password is sent or shown.
What is not done, or not proven
We prefer to say it plainly.
- The SAML flow has not been tried end to end with a real identity provider; OIDC is the best-proven path. Keep a local owner account as a break-glass.
- Imposed rules do not cover the rule overrides, exceptions or custom rules of a site. A provider does not share its integrations downward.
- The Agency (multi-client) licence sets a ceiling of sites and nodes for all its clients together; ToutWAF invoices nobody, and the legal texts for resellers are not written.
- Sending invitations was proven against a local test SMTP server, and the grace period of an archived client by moving the end date back, without waiting for it. Nothing ran against a real ToutPanel.
Use cases
An agency managing its clients' sites
One organisation per client, a read-only Client role for them, and a monthly report in their name next to ToutWAF.
A three-person security team
An analyst, an approver and an owner: nobody puts a blocking rule live alone.
An access audit
You verify the log chain over the period, export the entries and prove who changed the policy.
What is included, by edition
The basics are free; the advanced options need a paid offer. An option under licence stays visible in the console, locked, never hidden.
EditionFree Included in every offer, including both free offers (Free and Free +)Pro and above Paid offers: visible in the console, locked without a licence. From Pro, unless Agency or Enterprise is shown
Not yet tried in real conditions Works in the product's tests, but has not yet been tried with the real service, system or equipment. The console shows the same note where you set the function up.
Administration and access
- Roles and permissions: seven built-in roles, custom roles, scoping by site (2 users in the free edition)Free
- TOTP two-factor authentication with recovery codes, and API tokens with limited scopesFree
- Audit log: who, what, when and from where, with before and after, a verifiable hash chain, CSV, JSON and NDJSON exportFree
- Audit log exports in CEF and Syslog for a SIEMPro and above
- Enterprise sign-in: OIDC and SAML providers and SCIM provisioning Not yet tried in real conditionsEnterprise
- REST API for everything the console does, with scoped tokensFree
- Command-line tool: policy, tests, simulation, backups, diagnosticsFree
- Fleet page: nodes, versions, enrolment tokens and orchestrated updates of the nodesFree
- Licence: a signed key checked on your machine, with no check over the network; at expiry, 48 hours of grace then 48 hours of read-onlyFree
Tenants and MSPs
- One organisation, the default one, is included in the free editionFree
- Add a client wizard: client, quotas, first user, report brand, isolation check and handoverAgency and above
- Strict isolation between clients, checked by tests on every family of routesAgency and above
- Quotas per client (sites, users); the monthly volume of requests is measured and never cuts trafficAgency and above
- Client selector and a multi-client overview with the protection state of each clientAgency and above
- Suspend, archive, export and delete a client; reactivating, exporting and deleting are never lockedAgency and above
- Moving a site from one client to anotherAgency and above
- A policy floor imposed from aboveAgency and above
- Invitations by single-use link: no password is ever sentAgency and above
- PDF reports per client, scheduled; usage export in CSV for your own invoicingAgency and above
- The client's name, logo, colours and support contact on its reports, next to ToutWAF and never in its placeAgency and above
- Reseller licence: one pool of quotas shared by all your clientsAgency and above
Going back to the default of an advanced option is always possible. What happens when a paid licence ends is described in the pricing FAQ: 48 hours of grace, 48 hours of read-only, then WAF protection is switched off until renewal.
Pricing Read the documentation
Put a shield in front of your applications today
Install it on your own server, or get in touch to talk about licences.