24/7
Always on.
Nights, weekends, December. There is no meter to watch and no reason to switch it off at six. A slot is reserved for you, so a busy hour for someone else is not a slow hour for you.
Most AI is billed by the word, so the more your team uses it, the less you can predict what it costs.
Most AI services charge by usage. It sounds fair, until you see how usage really grows.
AI services count text in small pieces called tokens. Every question you ask and every answer you get is measured and billed.
The assistant does not remember on its own. Every time you write, the whole history is sent again, and billed again. The longer the conversation, the dearer the next question.
An assistant that works on its own reads, checks, retries and tries again, and each step is billed. One stuck loop at three in the morning becomes a line on the invoice.
When every question costs money, people ask less, finance asks questions, and the AI you set up sits unused.
A budget needs a number you can know in advance.
A meter cannot give you one.
Pick a situation or set your own numbers. We work out what usage billing adds up to at list prices, and how many slots you would need instead.
Per-token prices are the OpenRouter list for Qwen3.8-27B on 11 October 2026: typical provider $0.15 per million tokens in, $1.875 out, $0.0375 cached; cheapest listed $0.04, $1.35, $0.018. Converted at €0.92 per $1. With caching on, 80% of the context is billed at the cached price. Slots are estimated at 15 seconds per request, a peak three times the average, and a slot busy at most 60% of the time. Your numbers will differ: this is arithmetic, not a quote.
A slot is one answer at a time. It is not a person, and it is not a seat.
10 people×30% peak=3 in flight→4 slots
Typical chat-assistant seats are priced per person, and they are not private by contract. A slot is shared by the whole desk.
Agents are the exception: they can stay on a question for hours. If the desk is agents, plan one slot per agent that stays hot, or one for every two that take turns.
NEURA Brain is private AI for a fixed monthly fee. You reserve slots, a slot being one answer at a time, and use it as much as you like.
24/7
Nights, weekends, December. There is no meter to watch and no reason to switch it off at six. A slot is reserved for you, so a busy hour for someone else is not a slow hour for you.
Fixed
Every word, every retry and every loop is included. Finance writes one line in January, and it is still true in December.
Private
What you send answers you and builds your own memory, nothing else. Hosted in the European Union, operated by IANUSTEC S.R.L. in Italy, with a DPA.
Uncut
The model reads long files in full. When a conversation outgrows it, IANUSTEC keeps the whole history and brings back what each answer needs, instead of cutting the oldest turns.
These come from IANUSTEC's own assistant: Open WebUI with tools connected to Odoo, Nextcloud, email, calendar and a browser. Many tool calls, long results, private data. That is the work the endpoint is built for.
The assistant lists the month's calendar events, finds the company vehicle in Odoo, works out the trips and writes the odometer entries. One real conversation: about 90 tool calls, each result longer than the question that started it.
Real task, run in our assistantIt reads the inbox, opens a forwarded email and its attachment, and searches the shared folders for the matching practice. Documents that would never be pasted into a public chat.
Real task, run in our assistantIt reads the whole pipeline, counts by stage and revenue, and flags what has no activity. Measured in September 2026: 167 leads analysed in about two minutes, with correct totals in 9 runs out of 9.
Measured, September 2026Overdue tickets, who has the most, the five most urgent with priority and due date. In our tests the dates came out right in 3 runs out of 3, on a list of 120 tickets.
Measured, September 2026It navigates, reads the elements on the page, clicks and fills in forms, one step after another. A single browser test in our assistant took 136 tool calls: exactly the kind of loop that is expensive on a meter.
Real task, run in our assistantOne private conversation per client or case, growing for months: files, emails, decisions. The model reads the file directly. When the history outgrows it, IANUSTEC keeps the whole conversation and brings back what each answer needs.
Law firms, accountants, consultancies, local governmentWe test the service with real, long chats and reasoning switched on, before launch. Here are the figures, and the limits that come with them.
On a conversation that is already open, with a long history behind the question, thinking begins in about a second (median 0.9 s, 95% of requests under 1.7 s). The written answer follows once the reasoning is done: typically 5 to 8 seconds.
Between 60 and 120 tokens a second, about 45 to 90 words, depending on how busy the pool is. The answer scrolls as fast as you can follow it.
Reading a 200-page conversation from scratch takes about 14 seconds. After that it stays warm, and every further message starts in about a second.
Earlier test, August 2026: 10,320 requests against a 166,000-token case file, every detail recalled, zero errors. On a paired statistical test (HotpotQA) the result was no different from giving the model the whole file.
| What happens | What to expect |
|---|---|
| A conversation you already have open | Thinking starts in about a second. Written answer in 5 to 8 seconds with reasoning on. |
| The first message after a pause or a restart | The conversation is read again: about 14 seconds for 200 pages. |
| More requests at the same moment than you have slots | They wait in a queue and start on their own. Past a maximum wait you get a clear retry response, never a silent failure. |
| Agents running back to back, without pauses | Tested: they keep writing at about 20 tokens a second or better. |
| The full service, with the IANUSTEC memory layer on top | Not in these figures yet. We re-run them on the complete service before launch. |
Serving engine measured 2-10 October 2026. Raw data under NDA, or we re-run it live on your own file, on a call. The method stays closed. The outcome does not.
European rules are not a page in the footer. They are how this is built. The work stays in the European Union. What you send answers your question and builds your own memory, and nothing else: no training, no dataset, no resale.
The answer is made in the EU. The country can change from one member state to another. The Union does not.
IANUSTEC runs this, from Italy, and a named company is accountable. That is the starting point of the Act, not a sticker added after launch.
Your conversation memory is kept for your account only, never used to train a model, and deleted on request or when the contract ends.
Where the work happens
Every pin is in the Union. The work can move from one EU country to another. It does not leave. The United Kingdom is on the map, and it is not a pin: we do not leave the Union to save money.
IANUSTEC holds them, so security and privacy stay on our side of the desk. NEURA Brain is a product of IANUSTEC S.R.L., Italy.
The certificates are the audit. The contract is the rest: a DPA is available, and your data is deleted on request.
Any client with a base URL field works. Paste the URL, a key and the model name, and keep the tools you already use.
from openai import OpenAI
client = OpenAI(
base_url="https://api.neurabrain.io/v1",
api_key="nr-sk-...",
)
resp = client.chat.completions.create(
model="neura-brain",
messages=[{"role": "user",
"content": "What did we decide about the Rossi contract in March?"}],
)
print(resp.choices[0].message.content) # same SDK, same call
curl https://api.neurabrain.io/v1/chat/completions \
-H "Authorization: Bearer nr-sk-..." \
-H "Content-Type: application/json" \
-d '{
"model": "neura-brain",
"messages": [{"role": "user", "content": "What was the penalty clause we agreed in March?"}]
}'
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://api.neurabrain.io/v1",
apiKey: "nr-sk-...",
});
const resp = await client.chat.completions.create({
model: "neura-brain",
messages: [{ role: "user", content: "Pick up where we left off" }],
});
https://api.neurabrain.io/v1
nr-sk-…
neura-brain
Plan one slot for each agent that stays hot around the clock.
These clients are free software, yours to install. We do not ship a chat app: NEURA Brain is the private endpoint they talk to.
Early access is open. Reserve the slots you need, at a price that stays locked for your first twelve months. A person at IANUSTEC writes back within 24 hours.
Not users. A slot is one answer at a time. In an office about one person in three is asking at any moment, so ten people usually need three or four slots. An agent that stays hot around the clock needs one of its own.
A founding price, locked in writing for your first twelve months. Nothing to pay until your slots are live.
Afterwards we tell you the regular price at least 60 days ahead, and you can leave.
Reserved. Someone at IANUSTEC will write within 24 hours. Nothing to pay now.
IANUSTEC also builds NEURA, a complete private AI infrastructure: software and hardware, on-premises or in our cloud, three redundant nodes. The applications are already there and there are no SaaS seats on top.
One system: chat, files, automations, admin and the machines they run on. Not a chat bolted onto someone else's cloud.
NEURA Rack in your office: data never leaves the building. NEURA Cloud if you want the same platform hosted by IANUSTEC. Same stack, you choose the perimeter.
Three identical nodes, no master. One fails, the others keep the company running. IANUSTEC watches the cluster, never the conversations.
Open WebUI, Nextcloud, n8n and the admin panel are included, integrated and maintained. Odoo, OpenProject and Chatwoot when you want them. No per-app seats.
Said plainly: today NEURA Brain is Qwen3.8-27B, an open-weight model from the Qwen team. It is the best balance of cost and quality we have found for everyday operations, which is exactly the job of this service. And it is only the beginning: we have just started, and the model behind the name will change as better ones arrive.
A 27-billion-parameter model that reasons before it answers, reads long files and calls tools. It is the same open model you could download yourself.
A model is a file. A service is a price, a queue, a memory and a contract. That is the part you buy, and it stays the same when the model changes.
Tested before we ship it: on our agent test battery (CRM analysis, ticket triage, coding tasks, 18 episodes) the build we serve scored no worse than the full-precision original. When a better model replaces this one we say so first, and we run the same tests.
Certificate