Installation and maintenance
Installation and maintenance
Your team of agents, up and running in three weeks. What you prepare, how it goes, the time it takes you, what it costs, and what the follow-up covers afterwards.
We only install in your company what has run at Nakama for at least two months, on a version that has run there for at least two weeks. Every month, the same version is checked, the tests replayed, the configuration reviewed.
The prerequisites
- Your mailbox and calendar on Google Workspace or Microsoft 365, with an administrator who creates the access, guided, in half an hour.
- An account with the model provider, in your name, with a key created in front of you and a spending cap (or an all-inclusive package, on request).
- The choice of hosting: as SaaS, hosted in Europe, nothing to install; in your cloud or on premises, a server we prepare with your IT provider.
- A named person to approve what goes out.
The four stages
A deliverable at each stage. Each stage stands on its own: nothing obliges you to go on, and what has been delivered stays yours.
-
Free
The written reply
You describe your line of work and what you would like to hand over. The written reply, approved before it is sent, says whether Starter is enough for you, whether an audit makes sense, or why not yet.
DeliveredOne written page, and one of three answers.
-
Three weeks
Starter: NakamaOS by default
The base team, ready to use: your tools plugged into your accounts, all set up by an application security specialist so that the agents do only what you allow. Every setting is recorded in your installation file.
DeliveredYour NakamaOS, its installation file, the hand-over, a follow-up review at thirty days.
-
Two weeks, then quoted
The audit, then custom work
A week of record-keeping, a two-hour session on your own cases, the map of your processes and the threat model, then a written verdict. €4,900, deducted from the project if you sign. Then we build the agents your processes call for.
DeliveredThe verdict, the map, the quote for custom work; then your agents, with their view and your dashboard.
-
Every month
Monthly maintenance
A checked version, tests re-run, the configuration checked, and a monthly bulletin, every total with its source. Exit is included.
DeliveredThe month’s bulletin, a session; on exit, your files and a signed record.
You can stop here. Prices are published on the Offers and pricing page, “from”, excluding VAT; the quote states yours, with the cost over 24 months. The AI model is paid on your account, or in an all-inclusive package on request.
The sequence, from D-21 to D+30
In service in three weeks, then a follow-up review at thirty days.
| When | What | Who |
|---|---|---|
| D-21 to D-1The baseline record | For these three weeks, you note what your weekly tasks cost you: sorting, replies, follow-ups. It is your starting point, to judge the time saved afterwards. | You |
| D-7The checklist | The access to prepare and the chosen hosting. As SaaS, nothing to install; in your cloud or on premises, the sheet for your IT provider, with its estimated time. | You, your IT provider |
| D-5The access and the key | Your administrator creates the access to the mailbox and calendar, guided, in half an hour; the model key and its cap are created in front of you. | Your administrator, guided |
| DGoing live | NakamaOS is put into service and set up with you, in a screen share you open; the version’s tests are re-run in front of you. | Nakama, on your screen |
| DThe hand-over | An hour and a half per person, including ten minutes on transfer fraud and the approval gesture. The installation file is approved. | You and Nakama |
| D+1 to D+10The bedding-in | Two twenty-minute check-ins. | Nakama |
| D+30The thirty-day review | A follow-up review: what runs, what you approve, the time saved shown in NakamaOS, what needs adjusting. If a process calls for an agent built for you, this is the time to talk about it. | You and Nakama |
Your time
About six hours over six weeks, then thirty minutes a month. An estimate, to be measured on the first installations.
The frictions, stated as they are
- In the software, the everyday screens are still in English; they switch to French before the first full-price customer.
- No phone app: the interface is designed for a computer screen.
- NakamaOS needs an account with Nakama, as long as the installed version cannot do without it; the date will be published on the blog.
What it costs
Prices are published, “from”, excluding VAT. Starter: a six-month commitment, then monthly. The AI model is paid on your account, or in an all-inclusive package on request.
- Starter
- €907/month for 6 months, then €490/month
- Audit
- €4,900, deducted from the project if you sign
- Custom
- Quoted after the audit, subscription from €1,500/month
- Sovereign
- On quotation
What the maintenance covers, and what it does not
The maintenance covers
- the month’s stable version, checked, and its update;
- the tests re-run on your version;
- a configuration check: tool catalogue, standing authorisations, connectors;
- the month’s diff: instructions, notes and missions added or changed;
- the bulletin, prepared by the agents and approved, and a session, monthly on full maintenance, quarterly on standard maintenance;
- a written reply to every question; for a vulnerability, a shut-off instruction within one working day;
- security fixes, never charged extra.
It does not cover
- the AI model, which you pay to your provider, on an account in your name (unless all-inclusive);
- the approval time of the named person;
- custom development, for a tool with no direct integration: a fixed price, written beforehand;
- on-call cover, 24/7 support, a response time in hours;
- an outcome: this is a best-efforts obligation, written into the contract.
How NakamaOS is kept in your company
Installed and set up by an application security specialist, checked every month: the stable version, the tests re-run, the configuration verified, the month’s diff of instructions and missions.
The monthly bulletin: totals only, days of use, drafts used, missions launched or failed, permissions granted or refused, incidents. In your company, it stays yours.
Outage, exit, closure
If NakamaOS or Nakama stops
Nothing goes out without approval, and nothing about your mailbox changes: it works as before. You switch the agent off yourself in two minutes.
When you stop
The exit is included. Within ten working days, at no charge: your work exported as open files, access revoked, copies deleted, the software uninstalled, a signed record.
If Nakama were to close
Three months' notice, a last security fix, an exit done with you. We do not leave an agent running that nobody looks after.
Who invoices you
Nakama, Sociedade por Quotas, Lda, NIPC 517321670, Portugal
The subcontractors are named in the data processing agreement: the model provider, under your contract (under ours with the all-inclusive package); the connectors, through Nakama’s servers and then Composio; the screen-sharing tool; and, as long as NakamaOS needs it, the host of the NakamaOS account.
Declared interests: the founder has another salaried job during the day.
Capacity
Few clients at a time, one installation after another: Nakama is one person’s company, and every installation must be checkable every month.
We install one company at a time, in the order of the waiting list.
The documents
Questions
What about my employees?
No message leaves a mailbox without its owner’s approval. An information note for employees comes with the installation, and we do not install NakamaOS on HR data.
On a Mac?
Yes, as SaaS: NakamaOS opens in the browser, on Mac as on Windows.
On the phone?
No phone app: the interface is designed for a computer screen. As SaaS, missions run on the server, even with the computer off.
The interface?
In the software, the everyday screens are still in English; they switch to French before the first full-price customer. The permission windows, confirmations and errors are already in French.
Updates?
One stable version a month, checked at Nakama before it reaches you; as SaaS, we deploy it; in your cloud or on premises, with your provider.
References?
No client name appears in our texts. What can be shown: NakamaOS as it runs at Nakama, the blog, and Nakama’s installation file on request.