Agent platform
Twelve services in production. Eight agent types — support, collections, appointments, after-sales and more — across WhatsApp, Telegram and webchat. Behaviour control, traceability and isolation by design.
Designing solutions with artificial intelligence
We design and build the whole solution: the architecture, how the data is handled, privacy, where it runs, what gets measured and which model is worth tuning. And when agents are the way, we do not start from scratch — Agentry, our agent management platform, is already in production.
Real autonomy inside a defined path
We start from the problem, not from the tool. These are the disciplines we bring to the table; which ones apply, and in what order, depends on what we find.
Our agent management platform.
When the solution involves agents, the work starts on a platform already running in production, not on a blank page.
See what it includesWe define what to automate, what to leave to a person and how it fits what already works. Sometimes the answer is an agent; sometimes it is a shorter process and a dashboard.
architecture · integration
We look at what your operation already produces — conversations, tickets, transactions — to find where time is lost, and we leave it measured: what resolves on its own, what is handed over and what each conversation costs.
exploration · cost per case · resolution
Masking of personal data, isolation per customer and access logs. Where it runs is your call, and that decision shapes the design from day one — it is not something bolted on at the end.
PII · residency · on-premise · air-gapped
Agents that complete a request end to end, connected to your systems, with behaviour limited to what the organisation authorised.
FSM · tools · channels
When the case justifies it, we tune a model on your data or deploy an open one in your infrastructure. When it does not, we say that too.
fine-tuning · open models · evaluation
The product much of the work stands on. Four layers inside one perimeter: the agent platform is in production; the next ones extend models, teams and infrastructure without stepping outside that control.
Twelve services in production. Eight agent types — support, collections, appointments, after-sales and more — across WhatsApp, Telegram and webchat. Behaviour control, traceability and isolation by design.
Multi-provider and open models running on client infrastructure, chosen agent by agent according to what each task needs.
Training so your organization can operate, configure and evolve agents without depending on us. The panel already allows it; the formal programme is on the way.
On-premise and air-gapped deployment already available. Certified hardware as an appliance is the next step — when we can sustain it operationally.
Four real cases. None is an FAQ chatbot: each completes an end-to-end process.
Early collections no longer depends on call centre size.
Less no-shows and reception focused on who is present.
Customers resolve alone, any time.
Less waiting and more time for what matters.
Straight answers, for the first meeting with procurement and risk.
Wherever you decide: our cloud to start in days, a dedicated cloud in the country you need with a residency contract, or your own server — even with no internet connection.
cloud · dedicated · on-premise
No. We do not train models on your conversations. The AI runs with your key or in your infrastructure, and our price does not go up with your volume.
your AI, your account
No. The database prevents it at the architecture level, customer by customer. Documents, cards and phone numbers are stored masked.
isolation · masking
Only who you allow, with per-role permissions and an immutable log. Every incoming message is HMAC-verified and credentials are encrypted.
roles · HMAC · encryption
Yes. Conversations and traces are exportable at any time. Nothing is held hostage.
exportable
Nobody signs with an anonymous vendor. Here is what you need to know.
We are Dendra. We have built enterprise software for years, and on every artificial intelligence project we hit the same wall: the business wanted to automate a complete request, and risk asked what would happen if the model promised something the company could not deliver. Nobody had a good answer.
So we turned the problem around: instead of asking the model to behave, we built Agentry, where going off-script is impossible. But Agentry is the foundation, not the whole catalogue — before proposing an agent we look at the whole problem, and if the shortest path is another one, we say so.
What they will look for when you forward this page.
Example: a collections case, step by step
Each state declares valid transitions; model output is validated against that set before it is applied.
FSM · 4 state types · type validation
Event per state entry/exit, model call and tool invocation, with prompt, latency, tokens and cost.
trace events · prompt_version · cost_usd
RLS in Postgres, tenant prefix in Redis, own collection in Qdrant. tenant_id resolved once at the gateway.
Postgres RLS · Redis · Qdrant
HTTP with allowlist, read-only SQL, scripts in a restricted environment. Encrypted credentials.
http · db_query · AES-256
Per agent: commercial provider with client key or open model on their infrastructure.
OpenAI · Anthropic · Gemini · local
Metrics, logs and traces on an open stack, integrable with your current observability.
OpenTelemetry · Prometheus · Loki
It happens often. Many problems are solved by better data handling, a missing integration or a dashboard nobody built. We say so in the assessment, even when it means selling less.
A button tree only answers what was foreseen. This understands what the customer writes, queries your information and completes the process. The difference shows in the edge case.
A first agent on a bounded case is usually a matter of weeks; what stretches the timeline is access to internal systems and security review. After that, the day to day — configuration and copy — is handled from a panel: your systems team gets involved once, at the start.
They go to your team with the full conversation, in a prioritized queue. The customer stays in the same chat, repeating nothing.
Solution design is billed per project, with a written and bounded scope. Agentry is an annual subscription per agent in production, plus support level. AI usage you pay to the provider: our price does not go up with your volume.
Thirty minutes. Bring the process that takes the most time from your team.