Znote has always been a personal tool: your files, your key, your machine. That works beautifully for one person. It falls apart at fifteen.
Because the moment a company wants AI in everyone's notes, someone has to create fifteen API keys, paste them into fifteen machines, and hope nobody commits one to a repository. Nobody knows what it costs until the provider's invoice lands. And when someone leaves, that key is still out there.
So we've spent the last weeks on the other side of the product: Znote organisations.
One console, not fifteen keys
An organisation is your company inside Znote. You open it at organisation.znote.io with your work address, and you get a place to decide who uses AI and how:
- Your people, by email. Declare the email domains your company owns — subsidiaries and contractor domains included — and add people by address. Nothing to install on their machines.
- Seats. A number of employees allowed to use the AI, agreed with us. You see how many are taken, you ask for more when the team grows.
- Models. Pin the exact models your teams may use, or let them follow the default.
- Our key, or yours. Use the AI we provide and get a single invoice, or ask us to switch your organisation to your own OpenAI key and pay your provider directly.
- Usage you can read. Calls and tokens per person, per month. You know what AI costs your company before the invoice — and which teams have actually adopted it.
What it looks like for an employee
Nothing to configure. They open Znote, sign in from the account button in the bottom bar with their work email, and your company appears in the AI provider selector as znote (Your company).
They pick it, and every AI feature runs through your setup: @-context, slash prompts, tool calls, transcription. No key to paste, no settings to explain in an onboarding document. If they were already using their own OpenAI key for personal notes, it's still there — they just have one more provider to choose from.
The notes never leave the machine
This part didn't change, and it's the reason companies look at Znote in the first place.
Notes stay what they've always been: plain .md files on your employees' disks, on your network shares, wherever you already keep them. There is no vault to migrate, no proprietary format, no sync. Only the request an employee explicitly sends to the AI travels — the same request that would go to the provider anyway. We record how much was consumed, never what was written.
And if you stop, your teams keep Znote, keep every note, and switch back to their own key. There's nothing to export because nothing was ever taken.
Pricing, plainly
A flat plan from 5€ per seat per month: the same amount every month whatever your teams consume, one line in your budget, no meter to watch. The price per seat comes down as the team grows.
Anything that doesn't fit, we quote: billing on real usage instead of per seat, your own models or a private endpoint, your infrastructure, a specific tool wired into Znote. Tell us how your company buys and we'll work with that.
A refocus, not a pivot
Znote remains what it is — a beautiful local-first Markdown editor with AI and runnable code inside your notes, free for everyone. Nothing gets worse for individuals; the editor is the same, your key is still yours.
What changes is where our attention goes. The most interesting things people build with Znote are increasingly built together: a team's runbooks, a squad's standup notes, an analyst's reports that a whole department reads. Serving that properly means giving companies the controls they need instead of pretending they don't exist.
Try it before we talk
You don't need to speak to anyone to see how it works. Create your organisation at organisation.znote.io, invite a first team of ten or twenty, and look at the real usage after two weeks. That's a much better basis for a conversation than any quote we could write in advance.
Details on znote.io/company.html, or write to contact@alc-digital.fr.
Znote is a local-first Markdown editor with executable code blocks and AI grounded in your notes. Opens Obsidian vaults natively.