Azziz is the only human at Nakama. The eleven roles below and the code agents do everything; nothing goes out without approval.
Founder, application security expert
The only human at Nakama: the founder, an application security specialist. Azziz approves what goes out.
Meet the founderEleven roles, one piece of software. A role is a job description placed at the top of every message: all eleven share the same tools, and permission is granted tool by tool. Each role is named by its function; its first name follows, as the app displays it.
in the app
AI agentHe takes each request and hands it to the right specialist. Every morning, he says what is waiting for a decision.
In NakamaOSThe Today screen: what is waiting, the day’s calendar, the night’s missions.
AutomatesHanding each request to the right specialist, the morning brief, invoicing and admin: the month’s invoices, payment reminders, deadlines. It has no rights of its own. Invoicing and admin: approved before it goes out.
in the app
AI agentShe keeps the inbox: what is waiting for a reply, what is waiting on others, what can wait.
In NakamaOSThe Inbox screen, connected to Gmail and Outlook.
AutomatesThe inbox triage every morning; messages still unanswered after more than five days, flagged; on request, one reply drafted per message, and the follow-up. E-mail: approved before it goes out.
in the app
AI agentShe prepares the LinkedIn and X posts, plans the week’s content and suggests ideas drawn from the news.
In NakamaOSThe Marketing screen, connected to LinkedIn and X.
AutomatesThe LinkedIn and X posts, the week’s calendar, the notes of the week for the blog article, one note turned into a post per channel. Communication: approved before it goes out.
in the app
AI agentHe looks for prospects, prepares an angle and a first message, and tracks the pipeline and the follow-ups.
In NakamaOSThe Sales screen, connected to HubSpot and Gmail, and the built-in browser.
AutomatesThe written reply to requests, prospect profiles, first messages, the follow-up list, the CRM kept up to date. Prospecting: approved before it goes out.
in the app
AI agentShe sorts the tickets, drafts the replies and spots the question that keeps coming back, to turn it into a help article.
In NakamaOSThe Support screen, connected to HubSpot, Zendesk and Slack.
AutomatesSorting support requests, one draft reply per request, the help article on the question that keeps coming back. NakamaCyber support: approved before it goes out.
in the app
AI agentHe searches the web and reads pages, including those where a session is open, then reports back a sourced summary.
In NakamaOSThe built-in browser and web search. No connector.
AutomatesMonitoring, with the missions; a sourced summary, a comparison with a recommendation. Monitoring: approved before it goes out.
in the app
AI agentShe turns a routine, “every morning, do X”, into a mission: a dashboard that updates itself.
In NakamaOSThe Automations screen: the missions, their last run, the pause button.
AutomatesRoutines turned into missions, including SEO, site monitoring and the morning monitoring run, each with its dashboard in a note. SEO and site monitoring: approved before it goes out; Monitoring: approved before it goes out.
in the app
AI agentHe keeps the week’s figures: what the agents handled, the engine counters, the e-mail activity.
In NakamaOSThe Optimize screen. No connector.
AutomatesThe weekly review and its counters, each with its source. Analytics Lead: approved before it goes out.
in the app
AI agentHe keeps the knowledge base: notes, people, organisations, projects, meetings. He finds the right note when asked.
In NakamaOSThe Memory screen. No connector.
AutomatesThe right note, the right person, the right decision, for any agent that asks.
in the app
AI agentHe prepares every meeting: who is coming, the history, the open points. Afterwards, he draws out the decisions and actions.
In NakamaOSThe Meetings screen, connected to Google Calendar and Outlook.
AutomatesA brief before each meeting, minutes afterwards, from imported meeting notes.
in the app
AI agentHe looks at the calendar: the day, the free slots, the week’s load. He suggests blocks of time to protect.
In NakamaOSThe Planning screen, connected to Google Calendar and Outlook.
AutomatesThe plan for the day, suggested time slots, the week’s load.
One role per function; the Chief of Staff hands each request to the right specialist. In your company, the roles follow what your trade needs.
The code workshop
Code is not an agent role. Code agents plan, write and test on a branch; commits written by an agent carry its mark. That is how NakamaOS, our online cybersecurity service, and this site are written.
They run in a version of NakamaOS geared to development, used at Nakama. Shown, not sold.
Automates. The code and its tests, on a branch; the pull request with its report. Code and updates: approved before it goes out.
What keeps the agents in check is not in their job description. The software applies it, the same for all eleven; here are its default settings, those of the version installed in your company.
By default, a tool that only reads goes through without asking. A tool that writes, sends or publishes stops and waits for an answer: refuse, once, for the session, or always. Web search and reading a page also go through without asking: a known exit path, whose closing is an open ticket.
Permission is granted tool by tool and applies to every agent. An “always” grant removes the question for that tool; it is written in a file that can be read back.
The folder holding the permissions, the keys and the session is closed to the agents, for reading as for writing: an agent cannot grant itself a permission.
Every message is classified confidential, sensitive or public. At the confidential level, calls to a second model go to a local model; the main conversation stays on the chosen model.
Every conversation is recorded event by event: messages, tool calls, permission requests and answers.
A background mission has a reduced tool set and stops after 8 minutes by default, a limit that can be set mission by mission. It cannot obtain any permission: a tool that asks for one blocks it until it fails, unless that tool is allowed “always”.
Agent security: the engine, permissions and log.
Read the security rulesThe complete NakamaOS, installed in your company in three weeks: the same roles, ready to use, then cut to your trade; a person in your company approves what goes out.
Tell us what you need: the written answer is free. It says whether an audit makes sense, €4,900, deducted from the project if you sign.