Different teams, same instinct: own the tool, keep the data.
Tenon is deliberately general: projects, docs, chat and AI are what every team needs. What changes is the vocabulary, the compliance rules, and whether the right home is Tenon Cloud or your own servers. Pick your industry for a page written in your terms, with three project setups you can copy.
Written in your vocabulary, with projects you can copy.
Project playbooks
Product launch, website redesign, campaign, client onboarding, compliance audit, event, hiring, research study: complete board, field and page setups.
Five situations we see most often.
Everything a small team needs, free, running before lunch.
You don't have an IT department, a procurement process, or patience for a four-tool stack. Tenon Cloud gives a team of five a tracker, a wiki, chat and an AI assistant in one place (free, hosted, isolated) and grows with you to Team and Business.
Recommended: Tenon Cloud: Free, then Team
- Two-minute setupSign up with Google, name the workspace, invite the co-founders. No servers, no config.
- One place from day oneThe spec, the ticket and the decision live together, so the story of every feature is findable when you're fifty people.
- Brain on your termsConnect Gemini or OpenAI in a minute; switch to a self-hosted model later if a customer asks.
- Move on-prem laterIf an enterprise deal demands self-hosting, export the organization and deploy it. Same schema.
A four-person startup runs product, engineering and investor updates in one Cloud workspace. When their first enterprise customer asked "where is our data?", the answer was a region and an RLS policy, not a shrug.
Illustrative scenario
One deployment. One organization per client. Zero mixed-up data.
Agencies live in other people's data, and in the fear of pasting the wrong client's document into the wrong channel. Self-hosted Tenon gives each client their own isolated organization on a single deployment you run: unlimited organizations, no per-client fees.
Recommended: Self-hosted Enterprise
- Separate organizations per clientTickets, pages, chat and files are partitioned by Row Level Security. Your team switches between clients; nothing leaks across.
- No per-client fees when self-hostedSelf-hosted Enterprise is priced per deployment. Onboard the hundredth client for the same licence as the first.
- Share without loginsSend a client a public page link for the proposal, the status report or the launch checklist. Revoke it when the engagement ends.
- See the whole book of businessThe portfolio health table and resource heatmap show every client project and who is stretched thin, across clients, not just within one.
- Bill for the tool, not four toolsOne licence, your infrastructure. No per-client seat sprawl across a tracker, a wiki and a chat app.
A 30-person digital agency runs 14 client organizations on one self-hosted deployment. Account leads use insights to spot the over-committed designer before the client does; every proposal is a public share link instead of a PDF attachment.
Illustrative scenario
Sprints, specs and standups in the same place, with an AI that's read them.
Engineering teams have the worst case of tool sprawl: a tracker for tickets, a wiki for specs, chat for everything else, and an AI tool that's seen none of it. Tenon puts the spec next to the ticket and the decision next to both.
Recommended: Tenon Cloud Team, or self-hosted
- Boards and hill chartsKanban for the sprint; hill charts for the honest conversation about what's still being figured out.
- Specs that link to ticketsWrite the design doc as a page inside the project. Link it from the tickets it spawns. Backlinks show what still depends on it.
- Standups without the meetingAsync standups on a schedule, with an AI digest posted to the channel.
- API and webhooksWire Tenon into CI, HR, or your own tooling. Signed payloads, retries, a delivery log.
A 14-person mobile team replaced its tracker, wiki and chat with Tenon. The engineering manager's weekly check-in dropped from 40 minutes to four, because stuck tickets are flagged automatically and the status report writes itself.
Illustrative scenario
Data residency, no subprocessors, and AI that never leaves the building.
Healthcare, finance, legal, defence and government share a constraint: the work can't live in someone else's cloud, and "we use AI" can't mean "we send it to a vendor". Self-host Tenon: region-pinned, air-gap capable, with the AI assistant running on a model inside your network.
Recommended: Self-hosted Enterprise
- Your region, your serversSupabase Cloud in the region you choose, or the open-source stack on your own hardware. Air-gapped deployments are supported.
- SSO with your identity providerSAML or OIDC per workspace, enforced. Sessions visible and revocable; activity logs kept in your database.
- Self-hosted AIPoint Brain at Ollama, vLLM or your inference cluster via any OpenAI-compatible endpoint. No prompt leaves the network.
- Provable isolationRun the RLS self-test and attach the output to your audit evidence.
A healthcare services group runs Tenon on-premises with a local Llama model. The security questionnaire's "does data leave your environment?" question gets a one-word answer.
Illustrative scenario
Standardise internal tooling without standardising on a vendor.
Every department has its own tracker, wiki and chat. IT gets the bill, the security reviews and the "can you export our data?" tickets. Self-hosted Tenon lets you offer one platform on infrastructure you already run, with each department as its own isolated organization.
Recommended: Self-hosted Enterprise
- Departments as tenantsFinance, HR, Engineering and Marketing each get an organization. Superadmins manage all of them from one panel.
- Boring to operateStatic files plus Supabase. Backups with pg_dump, upgrades by deploying a folder and running migrations. No exotic runtimes.
- Admin broadcastsAnnounce maintenance windows and policy changes to every user from the superadmin panel.
- Verify your deploymentTest-email and RLS self-test functions confirm the setup before anyone logs in.
A 120-person company consolidated five departmental tool subscriptions into one Tenon deployment on their existing cloud account. Onboarding a new department is creating an organization and connecting SSO.
Illustrative scenario
Don't see your team here?
Tell us how you work and what constraints you have. We'll tell you honestly whether Tenon fits, and whether Cloud or self-hosted is the better answer.