In Kringl your whole team works with the same Kringls, in one place. What the organization knows is kept and enters every conversation, each person sees only what they are allowed to, and the work is connected to the tools you already use.
What changes when the AI belongs to the organization
A private chat helps one person. An organization needs its knowledge, its permissions and its work to stay with it.
The organization in Kringl
Each employee with a chat of their own
Knowledge
Kept in the organization and brought into every new conversation
Stays in the chat of whoever asked
Working methods
Written once, and the whole team works by them
Everyone explains them again, their own way
Permissions
Per person and per repository
Each person decides alone what to paste into a chat
Passwords and keys
In an encrypted vault, requested by name
Pasted into the chat
The work itself
Done to the end: code, checks and deployment
An answer someone still has to carry out
Control
A person approves before a change goes in, with a spending cap per person
No single place that shows who did what
Kringl works on top of Claude, Codex and Cursor: each person on the team connects the subscription they already have.
What you get
Four things every organization needs
1
Knowledge stays in the organization
What was learned in one conversation stays after it closes.
Memory that carries from one conversation to the next
Shared lessons gathered from every conversation, with search
Your working methods written once as a skill, personal or for the whole team
A topic: a folder across projects and people, with a shared memory
2
Each person sees what is theirs
Work together without everything being open to everyone.
Permissions per person and per repository
A meeting room where people and the Kringls talk
Every piece of work is recorded under the name of whoever asked for it
Share a project with another organization, by an email invitation
A personal area for each person
3
Connected to the tools you already use
The Kringls work where your work already is.
GitHub, GitLab and Bitbucket
An event in Slack, Jira, Monday, Sentry or Azure DevOps opens a conversation
Each person's Gmail and Google Drive, and a mail goes out only after a person presses send
Your own MCP servers, pinned by the manager to specific people
A public API with a key for each team member
4
The manager knows what is going on
An isolated environment, and a person who decides where it matters.
An isolated environment for each organization, with an encrypted vault
Two-step verification and remote device sign-out
A review board: a person approves before a change goes in
A spending cap per person: monthly, daily and per conversation
A gate of your own: your server sees every conversation that opens, and can stop it or add knowledge to it
Getting started
Four steps, and the team is working
1
Open a workspace
Sign up, open a workspace for the organization and invite your people. Each person is a seat.
2
Connect your tools
The repositories, Slack, Jira and mail. Each person connects their own accounts.
3
Write down your way
The organization's working methods and knowledge go in once and accompany every conversation. Settings you already have in Claude Code, Codex or Cursor are imported with one command.
4
Hand over work
Everyone asks in their own words. The Kringls do the work, and you see what was done and approve it.
Writes the code, checks it and deploys it, within the permissions of whoever asked.
OperaPlanner
Turns a manager's request into a spec that can be built from.
BillInfrastructure manager
Looks after the servers, the database and the backups.
Questions
What people ask before bringing it in
Does Kringl replace Claude, Codex or Cursor?
No. Kringl works on top of them: each person on the team connects the subscription they already have, and the Kringls work through it. Someone without a subscription can work with Kringolus.
Who sees our code and our knowledge?
Only your people. Each organization works in an environment isolated from every other organization, and repository permissions are set per person. Passwords and keys are kept in an encrypted vault and are never typed into a conversation.
How is the organization's knowledge kept?
In three layers: each person's own memory, shared lessons gathered from every conversation, and skills where the working methods are written. What belongs to a topic enters every conversation in that topic.
Can we require a person's approval before a change goes in?
Yes. The review board holds every change until a person approves it, and each routine gets its own level of autonomy, hours and days.
Can Kringl connect to our systems?
Yes. There is a public API with a key for each team member and signed webhooks, and you can connect MCP servers of your own. An event in Slack, Jira or Monday opens a conversation by itself.
How do we pay?
Per seat. A seat is one person in the workspace, and the first 14 days are free. The manager sets a spending cap per person.
Which languages does it work in?
Hebrew, English, Arabic, Russian and French, in the browser and on the phone.
Talk to us
See it on your organization
Leave your details, and someone from the team gets back to you for a short conversation about your organization.
Got it
We'll get back to you at the mobile number you left.
One organization, one team
Open a workspace, invite your people and see for yourselves.