Privacy compliance for every customer you have. Under your name.
Agencies, resellers, and platforms use Katla’s API and MCP server to scan, classify, and prove consent across hundreds of sites at once. You keep the relationship; we keep the cookies in line.
Every client site, one dashboard, one invoice.
Create a team per client, add their sites, and give your staff and the client access to just that team. Scheduled rescans catch what changes between your check-ins, so compliance becomes something you can actually deliver on a retainer.
- Billing
- One invoice, priced per site
- Organisation
- Teams per client, roles per team
- Reporting
- CSV and JSON export per site
Add domains however you work
Through the dashboard, the CLI, or the API. Each one gets verified, scanned, classified, and a draft privacy policy you can publish or embed.
Rescans on a schedule, not a reminder
Pro rescans monthly, Business weekly. The next scan shows the delta, so a pixel someone dropped in last week is on the report rather than in a surprise.
Your brand on the banner
Whitelabel is included on every paid plan: the consent banner and policy pages carry your colours and no Katla mark.
Volume pricing as you grow
Per-site pricing on the published plans, or negotiated volume pricing on Custom once the portfolio justifies it.
Pick the integration that matches your team.
All three drive the same platform, and you can mix them — provision over the API, check a client’s cookies from the dashboard, and let an assistant do the classification.
Teams
▾ Acme Group (12 sites)
acme-shop.se Scan 2h ago ✓ verified
acme-b2b.se Scan 2h ago ✓ verified
▾ Nordic Dental (4 sites)
nordic-dental.dk Scan 1h ago 3 uncategorised
▸ Retainer clients (38 sites)
▸ Hosting plan · Pro (88 sites)
[ + New team ] [ Add site ] [ Invite member ]Roles per team: owner, admin, member
What you get.
Volume pricing
Published per-site pricing up to Business, and negotiated volume pricing on Custom once a portfolio justifies it.
Whitelabel banner and policies
Included on every paid plan. Your colours, your copy, and no Katla mark in front of your client’s visitors.
Service accounts
A machine-to-machine key per team so your backend provisions sites, queues scans, and reads consent records without a human login.
Teams and roles
Group sites by client, brand, or region. Owner, admin, and member per team, so a client sees their sites and nothing else.
The same API and MCP server
No separate partner product to learn or wait for. What you integrate is what every Katla user already runs.
DPA, SLA, and EU hosting
A signed data-processing agreement and an uptime SLA come with the Custom plan. Everything is hosted in the EU.
Four steps, not a procurement cycle.
- 01
Talk to us
A short call about your portfolio, how you want to bill, and which of the three integration paths fits.
- 02
Get a service account
On the Business or Custom plan, an admin issues a key from team settings. Scoped read or write, revocable, and rotatable without downtime.
- 03
Brand and integrate
Theme the banner per site, then wire the API into your provisioning so a new client becomes a team and their sites get scanned.
- 04
Go live
Import your first clients and review the first scans together before you put your own name on the output.
The ones partners actually ask.
- Is there a separate partner dashboard or API?
- No, and that is the point. Partners use the same dashboard, the same REST API, and the same MCP server as every other Katla user. Teams are what make it work at scale: group sites by client, brand, region, or hosting plan, and give each person access to only the teams they need.
- What is a service account?
- A team member that is not a person. It holds an API key instead of a login, carries its own role and scopes, and is bound to one team for its whole life. Your backend uses it to add sites, queue scans, and read consent records with no human in the loop. It is available on the Business and Custom plans.
- Can a service account create the team as well as the sites?
- Not today. Service accounts are refused on account administration — billing, team members, and creating or deleting teams — so a leaked key cannot restructure your account or mint itself more access. A person creates the team; the key provisions everything inside it.
- Do client sites need their own Katla accounts?
- No. Sites live in teams under your account. Invite a client as a member on their team and they see only their own sites. The roles are owner, admin, and member.
- Can I hide Katla from my clients?
- On the banner and policy pages, yes — whitelabel is included on every paid plan, so there is no Katla mark in front of your client’s visitors. The dashboard and the banner CDN still run on Katla domains.
- Is the MCP server available to my customers, or only my team?
- Both. Anyone connects with their own Katla account and sees exactly the teams they belong to, so a client invited to their own team sees only their own sites.
- Where is data stored?
- Consent records and scan results are hosted in the EU. A data-processing agreement is part of the Custom plan.
Bring your portfolio.
Tell us how many sites, how you bill, and what you want your clients to see. We will tell you honestly whether Katla fits.