Nexus

AI agents
that work under your rules.

Nexus brings quotes, orders, inventory, accounts and team workflows into one ERP. Its agents work on that data alongside your team, under approval and audit rules.

They notice the unanswered quote and the overdue invoice, and suggest what to do. On every step that reaches a customer, an authorised person has the final say.

Built to run Karea Bilgi Teknolojileri's own sales and operations. In production at two companies today.

Nexus · Suggestions
Sales Operations AgentL1 RecommendShadow mode · nothing changes07:31

Follow-up task for the Doğubey RES switchyard quote

The quote was sent on 12 Sep 2026 and has had no reply for 12 days. It expires on 30 Sep 2026.

TKL-2026-000142Doğubey Rüzgar Elektrik
Proposed actionCreate a follow-up task for Hasan Kaya dated 25 Sep 2026.
Is this proposal right?
TodayCollections noticed at month endWith NexusOn screen every morning
TodayQuotes kept in a salesperson's headWith NexusOn screen every morning
TodayApprovals waiting in e-mailWith NexusStraight to the right person
TodayScattered spreadsheetsWith NexusOne customer record

Because they fear losing control,
companies hold back from giving work to AI.

40%

of enterprises will demote or decommission autonomous AI agents by 2027 because of control gaps that surface in production.

Gartner, 26 May 2026

23.6%

of Turkish firms with 10-49 employees use ERP software. For small firms in the EU the figure is 41%.

TÜİK 2025 · Eurostat 2025

7.5%

of Turkish firms with 10 or more employees use AI. The EU average is 20%.

TÜİK 2025 · Eurostat 2025

The global platforms that offer governed agents either lack Turkish support or process data outside Türkiye. In local ERPs, AI is still limited to assistants that answer questions. Nexus is being built so you can give agents work and keep control.

An unanswered quote, a late collection, a forgotten follow-up...

About three in four Turkish firms with 10-49 employees do not use an ERP (TÜİK 2025). These follow-ups often depend on one person remembering.

Unanswered quote

The quote went out 12 days ago and nobody replied.
It is about to expire and no one noticed.

Lost sale

Late collection

An overdue invoice reaches no one's desk until the month-end report.

Cash tied up

Forgotten follow-up

The call-back promised in a meeting stays in someone's diary. Meanwhile the customer calls your competitor.

Lost customer

Agents take on the follow-up, and the final say stays with you.

Nexus agents are designed for three results.

No follow-up is forgotten

Quotes waiting for a reply and overdue follow-ups are found every morning. They reach the record's owner as a task or a notification.

Late collections become visible

Receivables 7 or more days overdue are found without waiting for month end. A payment reminder e-mail comes to you for approval.

Approvals do not wait

Requests waiting for approval reach the right person with the reason attached.

Three rules make this safe

An agent is a userIt sees only the data its role allows. It cannot sign in or approve its own request.
No direct database accessIt works through the same controlled actions a person uses. Every step that reaches a customer waits for a person's approval.
Autonomy grows with evidenceIt starts in shadow mode. Your administrator raises the level based on how its suggestions were rated.

What the agent does

The Sales Operations Agent checks six situations every morning.

The check runs every day at 07:30. When a quote is accepted, the agent looks again within minutes. Depending on its level, each finding becomes a suggestion, a follow-up task or an action waiting for approval.

1

A quote about to expire

FindsSent quotes whose validity is about to end.
At L2 and aboveA follow-up task. At L3, a revision or a reminder e-mail, with your approval.
2

Unanswered quote

FindsQuotes sent 7 or more days ago with no reply.
At L2 and aboveA follow-up task. At L3, a reminder e-mail, with your approval.
3

Overdue follow-up

FindsPromised follow-ups that were not done on time.
At L2 and aboveA notification to the follow-up's owner.
4

Accepted, not ordered

FindsAccepted quotes that have not become an order yet.
At L2 and aboveA follow-up task minutes after acceptance.
5

Stalled project

FindsOpen projects with no activity for a long time.
At L2 and aboveA follow-up task for the project's owner.
6

Overdue receivable

FindsInvoices 7 or more days past due.
At L2 and aboveA follow-up task. At L3, a payment reminder e-mail, with your approval.

Autonomy

You set each agent's authority across four levels.

The agent starts at L1, in shadow mode. An administrator sets the level, and every change is written to the audit trail.

L0Observe

Finds and counts the records that need follow-up. No model call, no cost.

Nothing changes

L1Recommend
Starting level

Writes a suggestion for each finding. An admin rates it Right or Wrong.

Nothing changes

L2Prepare

Also writes a follow-up task and a notification for the record's owner.

An internal task, logged under the agent's name

L3Execute

Puts the customer-facing step up for approval: a quote revision or a reminder e-mail.

A person approves; the action runs in their name

Act alone  Not offered in Nexus.

This matches the four autonomy levels Gartner recommends (Observe, Advise, Act with Approval, Act Autonomously).
Nexus deliberately does not offer the fourth level (Act Autonomously).

Workflow

Every agent run is on record from start to finish.

  1. 1

    Observe

    Every morning at 07:30, and when a quote is accepted, rule-based code finds the records that need follow-up. If there is nothing to find, the model is not called and the run costs nothing.

  2. 2

    Mask

    Company, project and quote names become random codes. Amounts are rounded and dates become day counts. Names, e-mails and phone numbers are never sent.

  3. 3

    Reason

    The summary goes to the model your company has approved, in a single call.
    The call passes through Cloudflare AI Gateway, which keeps no copy of the data.

  4. 4

    Suggest and decide

    The suggestion reaches an admin, who rates it Right or Wrong.
    At L2 a follow-up task goes to the owner; at L3 the action is put up for approval.

  5. 5

    Audit

    Each run records the model, the cost and the summary sent.
    Every agent action is written to the audit trail under the agent's name.

Every suggestion shows what the model saw

Fields sent to the model

  • quote no, as a code
  • company, as a code
  • project, as a code
  • amount, rounded
  • day counts

Fields withheld

  • legal name
  • contact name
  • e-mail
  • phone
  • tax id
  • notes

Route: Amazon Bedrock · Cloudflare AI Gateway

Data

Your customer's name never reaches the model.

The summary the agent sends does not reveal who it is about. Codes are generated fresh for every run, and the key to them lives in Nexus's memory only while the run lasts, then it is dropped.

The record in Nexus
QuoteTKL-2026-000142
CompanyDoğubey Rüzgar Elektrik Ltd. Şti.
ProjectDoğubey RES switchyard
ContactName, e-mail, phone
Amount₺118,460.00
Sent12 Sep 2026, no reply
The summary sent to the model
quote[Q-4TD]
company[C-7KQ]
project[P-2MX]
amount120,000 TRY
unanswered9 days

Example. In a breach, this is all anyone could see: "[C-7KQ]'s quote: 120,000 TRY, unanswered for 9 days."

Never sent
Company and contact names
E-mail
Phone
Tax number
Address
Notes
Follow-up titles
Record ids

Every field classified

Every column the agent reads is classed as coded, clear or never sent. An unclassified column stops the tests.

No copy at the gateway

The call passes through Cloudflare AI Gateway with request and response logging off. Cost is metered in Nexus.

Visible on every suggestion

The suggestion card shows which fields the model saw. The summary sent in each run is stored exactly as sent.

Platform

Under the agents sits an ERP already in production.

Ten modules share one customer record, one permission model and one audit trail.
The quote sales enters and the invoice finance tracks belong to the same account.

CRMCompanies, contacts, opportunities and follow-ups
SalesQuotes and orders
ProcurementPurchase requests and orders
InventoryProducts, warehouses and stock movements
FinanceAccount, invoice and collection visibility
HRStaff, leave and performance
TasksTasks, priority and capacity
AssetsEquipment, maintenance and certificates
FleetVehicles and tracking integrations
CustodyHand-over and return records
Invoices
FTR-2026-000517Baltacıoğlu Metal San. ve Tic. A.Ş.1 Sep 2026TRY 312,400.00TRY 162,400.00OverdueElif A.
FTR-2026-000664Karaduman Tekstil A.Ş.4 Sep 2026TRY 94,250.00TRY 94,250.00Reminder awaiting approvalSales Operations Agent
FTR-2026-000702Doğubey Rüzgar Elektrik Ltd. Şti.1 Oct 2026TRY 58,600.00TRY 58,600.00OpenElif A.
ALS-2026-004411Yeşilova Gıda Sanayi A.Ş.23 Aug 2026TRY 133,700.00—PaidMurat T.

Infrastructure

The infrastructure is designed to global standards.

UserIn the browser, in Turkish or English
CloudflareDDoS protection, firewall and access control
Your own installationIts own app, its own database, automatic HTTPS
AI GatewayHolds the cloud keys, keeps no copy of the data
ModelThrough Amazon Bedrock, Anthropic or Azure AI Foundry; the model your company approves
Cloudflare

AI exit and front door

Every model call leaves through AI Gateway. The gateway holds the cloud keys, so no AWS key sits on the server. No copy of requests or responses is kept. Next: a firewall and access control in front of every installation.

Amazon Web Services

Primary model route

Agents run on the model your company approves, through Amazon Bedrock. Bedrock does not store prompts and responses or use them to train models. Bedrock invocation logging is set off when the account is set up.

Microsoft Azure

Second route and identity

Azure AI Foundry is ready as a second route to the model. Automatic failover is planned. Sign-in with Microsoft work accounts is planned.

Platform security

Engineering measures running today in production installations.

Encrypted sessions

Live

The session cookie is encrypted and signed with iron-session. Page scripts cannot read it, and the session closes on its own after 12 hours.

HTTPS only

Live

Every installation is served with an automatic TLS certificate. HSTS forces the browser to use encrypted connections only.

Content Security Policy

Live

CSP lets only Nexus's own scripts run on the page. The page cannot be embedded in another site.

Client address cannot be spoofed

Live

The reverse proxy rewrites the client IP header on every request, so the sign-in limit cannot be bypassed with a fake header.

Containers per company

Live

The app, background jobs and database run in separate Docker containers for each company.

Tests on every change

Live

Every change passes a 148-scenario browser test suite. Database permissions are checked by their own tests.

Cloudflare, Amazon Web Services, Amazon Bedrock, Anthropic, Microsoft Azure and Azure AI Foundry are trademarks of their owners.

Security

The security layer was built before the agents.

Protection in four layers, from sign-in to database.

5failed tries and the account locks
2-stepsign-in with an authenticator app
7separate database roles
Every 6 hencrypted backup · in build
LiveIn build

Identity

Who signs in
  • Passwords are hashed with scrypt; plain text is never stored.
  • Two-step sign-in (TOTP). If the second step is not completed within 5 minutes, the password is asked again.
  • An escalating lock after 5 failed tries per user or 20 per IP address.
  • Open sessions are revoked at once when a password changes or access is removed.

Permissions

What a person can see and change
  • Role and business-unit scope is applied on every database query.
  • No one can approve their own request.
  • The agent is a user with its own role; it cannot sign in or approve its own request. · in build
  • Every step that reaches a customer waits for a person's approval. · in build

Data

How records are protected
  • Each company has its own installation and its own database.
  • Seven separate database roles: the app cannot change the schema or touch audit records.
  • The audit trail is chained and locked at the database level.
  • KVKK retention, erasure and data subject request flows.
  • Company names, contacts and contact details never reach the model; names become random codes. · in build

Continuity

If something is lost
  • An encrypted backup every 6 hours, in an account separate from production.
  • Backups are encrypted with a public key; the server cannot read old backups.
  • Target: at most 6 hours of data lost, working again within 4 hours.
  • Regular restore drills with recorded evidence.

Scenarios

What happens if something goes wrong?

A password is stolen

Sign-in fails without the second-step code. Guessing locks after 5 failed tries. Resetting the password closes every open session.

An employee tries to rewrite history

They can touch only the records their role allows. Not even the app itself can change audit records; if an old entry changes, the chain breaks and it shows.

The server is lost

Encrypted backups sit in an account separate from production. The target is to be working again within 4 hours, with at most 6 hours of data lost.

An agent makes a mistake

The agent works only through controlled actions and cannot approve its own request. Every step that reaches a customer waits for approval; internal follow-up tasks are logged under the agent's name. An admin stops the agent with one switch, which also closes its account.

The model provider has a breach

All that leaks is codes, rounded amounts and day counts: "[C-7KQ]'s quote: 120,000 TRY, unanswered for 9 days." The key to the codes stays in Nexus, and only while the run lasts.

The spending limit is reached

Each call is priced at its worst case before it is made. If the daily cap or the weekly allowance is used up, the agent does not run and the run is recorded in red.

Usage

AI usage is weekly and always visible.

The subscription is priced by the modules you choose, with one of three AI tiers on top. Each tier grants a weekly allowance that your team sees as a percentage. The allowance renews every Monday at 00:00.

Weekly AI usage62%
AI tier 2Renews Mon 00:00
Weekly AI usage86%
Usage is highRenews Mon 00:00
When the allowance runs outThe agent waits for the new week. Each call is priced before it is made, so spending never goes past the allowance.

We share module and tier prices in the demo, based on the scope of your installation.

Demo

See Nexus on your own processes.

Share how your team is organised and what matters most. In the call we show the platform on your own processes and work out together where agents would save your team time.

  1. 1Needs and process assessment
  2. 2Platform walkthrough tailored to your company
  3. 3Installation scope and agent roadmap
Your details are used only for this request.
Nexus

AI agents
that work under your rules.

Nexus brings quotes, orders, inventory, accounts and team workflows into one ERP. Its agents work on that data alongside your team, under approval and audit rules.

They notice the unanswered quote and the overdue invoice, and suggest what to do. On every step that reaches a customer, an authorised person has the final say.

Built to run Karea Bilgi Teknolojileri's own sales and operations. In production at two companies today.

Nexus · Suggestions
Sales Operations AgentL1 RecommendShadow mode · nothing changes07:31

Follow-up task for the Doğubey RES switchyard quote

The quote was sent on 12 Sep 2026 and has had no reply for 12 days. It expires on 30 Sep 2026.

TKL-2026-000142Doğubey Rüzgar Elektrik
Proposed actionCreate a follow-up task for Hasan Kaya dated 25 Sep 2026.
Is this proposal right?
TodayCollections noticed at month endWith NexusOn screen every morning
TodayQuotes kept in a salesperson's headWith NexusOn screen every morning
TodayApprovals waiting in e-mailWith NexusStraight to the right person
TodayScattered spreadsheetsWith NexusOne customer record

Because they fear losing control, companies hold back from giving work to AI.

40%

of enterprises will demote or decommission autonomous AI agents by 2027 because of control gaps that surface in production.

Gartner, 26 May 2026

23.6%

of Turkish firms with 10-49 employees use ERP software. For small firms in the EU the figure is 41%.

TÜİK 2025 · Eurostat 2025

7.5%

of Turkish firms with 10 or more employees use AI. The EU average is 20%.

TÜİK 2025 · Eurostat 2025

The global platforms that offer governed agents either lack Turkish support or process data outside Türkiye. In local ERPs, AI is still limited to assistants that answer questions. Nexus is being built so you can give agents work and keep control.

An unanswered quote, a late collection, a forgotten follow-up...

About three in four Turkish firms with 10-49 employees do not use an ERP (TÜİK 2025). These follow-ups often depend on one person remembering.

Unanswered quote

The quote went out 12 days ago and nobody replied. It is about to expire and no one noticed.

Lost sale

Late collection

An overdue invoice reaches no one's desk until the month-end report.

Cash tied up

Forgotten follow-up

The call-back promised in a meeting stays in someone's diary. Meanwhile the customer calls your competitor.

Lost customer

Agents take on the follow-up, and the final say stays with you.

Nexus agents are designed for three results.

No follow-up is forgotten

Quotes waiting for a reply and overdue follow-ups are found every morning. They reach the record's owner as a task or a notification.

Late collections become visible

Receivables 7 or more days overdue are found without waiting for month end. A payment reminder e-mail comes to you for approval.

Approvals do not wait

Requests waiting for approval reach the right person with the reason attached.

Three rules make this safe

An agent is a userIt sees only the data its role allows. It cannot sign in or approve its own request.
No direct database accessIt works through the same controlled actions a person uses. Every step that reaches a customer waits for a person's approval.
Autonomy grows with evidenceIt starts in shadow mode. Your administrator raises the level based on how its suggestions were rated.

What the agent does

The Sales Operations Agent checks six situations every morning.

The check runs every day at 07:30. When a quote is accepted, the agent looks again within minutes. Depending on its level, each finding becomes a suggestion, a follow-up task or an action waiting for approval.

1

A quote about to expire

FindsSent quotes whose validity is about to end.
At L2 and aboveA follow-up task. At L3, a revision or a reminder e-mail, with your approval.
2

Unanswered quote

FindsQuotes sent 7 or more days ago with no reply.
At L2 and aboveA follow-up task. At L3, a reminder e-mail, with your approval.
3

Overdue follow-up

FindsPromised follow-ups that were not done on time.
At L2 and aboveA notification to the follow-up's owner.
4

Accepted, not ordered

FindsAccepted quotes that have not become an order yet.
At L2 and aboveA follow-up task minutes after acceptance.
5

Stalled project

FindsOpen projects with no activity for a long time.
At L2 and aboveA follow-up task for the project's owner.
6

Overdue receivable

FindsInvoices 7 or more days past due.
At L2 and aboveA follow-up task. At L3, a payment reminder e-mail, with your approval.

Autonomy

You set each agent's authority across four levels.

The agent starts at L1, in shadow mode. An administrator sets the level, and every change is written to the audit trail.

L0Observe

Finds and counts the records that need follow-up. No model call, no cost.

Nothing changes

L1Recommend
Starting level

Writes a suggestion for each finding. An admin rates it Right or Wrong.

Nothing changes

L2Prepare

Also writes a follow-up task and a notification for the record's owner.

An internal task, logged under the agent's name

L3Execute

Puts the customer-facing step up for approval: a quote revision or a reminder e-mail.

A person approves; the action runs in their name

Act alone  Not offered in Nexus.

This matches the four autonomy levels Gartner recommends (Observe, Advise, Act with Approval, Act Autonomously). Nexus deliberately does not offer the fourth level (Act Autonomously).

Workflow

Every agent run is on record from start to finish.

  1. 1

    Observe

    Every morning at 07:30, and when a quote is accepted, rule-based code finds the records that need follow-up. If there is nothing to find, the model is not called and the run costs nothing.

  2. 2

    Mask

    Company, project and quote names become random codes. Amounts are rounded and dates become day counts. Names, e-mails and phone numbers are never sent.

  3. 3

    Reason

    The summary goes to the model your company has approved, in a single call. The call passes through Cloudflare AI Gateway, which keeps no copy of the data.

  4. 4

    Suggest and decide

    The suggestion reaches an admin, who rates it Right or Wrong. At L2 a follow-up task goes to the owner; at L3 the action is put up for approval.

  5. 5

    Audit

    Each run records the model, the cost and the summary sent. Every agent action is written to the audit trail under the agent's name.

Every suggestion shows what the model saw

Fields sent to the model

  • quote no, as a code
  • company, as a code
  • project, as a code
  • amount, rounded
  • day counts

Fields withheld

  • legal name
  • contact name
  • e-mail
  • phone
  • tax id
  • notes

Route: Amazon Bedrock · Cloudflare AI Gateway

Data

Your customer's name never reaches the model.

The summary the agent sends does not reveal who it is about. Codes are generated fresh for every run, and the key to them lives in Nexus's memory only while the run lasts, then it is dropped.

The record in Nexus
QuoteTKL-2026-000142
CompanyDoğubey Rüzgar Elektrik Ltd. Şti.
ProjectDoğubey RES switchyard
ContactName, e-mail, phone
Amount₺118,460.00
Sent12 Sep 2026, no reply
The summary sent to the model
quote[Q-4TD]
company[C-7KQ]
project[P-2MX]
amount120,000 TRY
unanswered9 days

Example. In a breach, this is all anyone could see: "[C-7KQ]'s quote: 120,000 TRY, unanswered for 9 days."

Never sent
Company and contact names
E-mail
Phone
Tax number
Address
Notes
Follow-up titles
Record ids

Every field classified

Every column the agent reads is classed as coded, clear or never sent. An unclassified column stops the tests.

No copy at the gateway

The call passes through Cloudflare AI Gateway with request and response logging off. Cost is metered in Nexus.

Visible on every suggestion

The suggestion card shows which fields the model saw. The summary sent in each run is stored exactly as sent.

Platform

Under the agents sits an ERP already in production.

Ten modules share one customer record, one permission model and one audit trail. The quote sales enters and the invoice finance tracks belong to the same account.

CRMCompanies, contacts, opportunities and follow-ups
SalesQuotes and orders
ProcurementPurchase requests and orders
InventoryProducts, warehouses and stock movements
FinanceAccount, invoice and collection visibility
HRStaff, leave and performance
TasksTasks, priority and capacity
AssetsEquipment, maintenance and certificates
FleetVehicles and tracking integrations
CustodyHand-over and return records
Invoices
FTR-2026-000517Baltacıoğlu Metal San. ve Tic. A.Ş.1 Sep 2026TRY 312,400.00TRY 162,400.00OverdueElif A.
FTR-2026-000664Karaduman Tekstil A.Ş.4 Sep 2026TRY 94,250.00TRY 94,250.00Reminder awaiting approvalSales Operations Agent
FTR-2026-000702Doğubey Rüzgar Elektrik Ltd. Şti.1 Oct 2026TRY 58,600.00TRY 58,600.00OpenElif A.
ALS-2026-004411Yeşilova Gıda Sanayi A.Ş.23 Aug 2026TRY 133,700.00—PaidMurat T.

Infrastructure

The infrastructure is designed to global standards.

UserIn the browser, in Turkish or English
CloudflareDDoS protection, firewall and access control
Your own installationIts own app, its own database, automatic HTTPS
AI GatewayHolds the cloud keys, keeps no copy of the data
ModelThrough Amazon Bedrock, Anthropic or Azure AI Foundry; the model your company approves
Cloudflare

AI exit and front door

Every model call leaves through AI Gateway. The gateway holds the cloud keys, so no AWS key sits on the server. No copy of requests or responses is kept. Next: a firewall and access control in front of every installation.

Amazon Web Services

Primary model route

Agents run on the model your company approves, through Amazon Bedrock. Bedrock does not store prompts and responses or use them to train models. Bedrock invocation logging is set off when the account is set up.

Microsoft Azure

Second route and identity

Azure AI Foundry is ready as a second route to the model. Automatic failover is planned. Sign-in with Microsoft work accounts is planned.

Platform security

Engineering measures running today in production installations.

Encrypted sessions

Live

The session cookie is encrypted and signed with iron-session. Page scripts cannot read it, and the session closes on its own after 12 hours.

HTTPS only

Live

Every installation is served with an automatic TLS certificate. HSTS forces the browser to use encrypted connections only.

Content Security Policy

Live

CSP lets only Nexus's own scripts run on the page. The page cannot be embedded in another site.

Client address cannot be spoofed

Live

The reverse proxy rewrites the client IP header on every request, so the sign-in limit cannot be bypassed with a fake header.

Containers per company

Live

The app, background jobs and database run in separate Docker containers for each company.

Tests on every change

Live

Every change passes a 148-scenario browser test suite. Database permissions are checked by their own tests.

Cloudflare, Amazon Web Services, Amazon Bedrock, Anthropic, Microsoft Azure and Azure AI Foundry are trademarks of their owners.

Security

The security layer was built before the agents.

Protection in four layers, from sign-in to database.

5failed tries and the account locks
2-stepsign-in with an authenticator app
7separate database roles
Every 6 hencrypted backup · in build
LiveIn build

Identity

Who signs in
  • Passwords are hashed with scrypt; plain text is never stored.
  • Two-step sign-in (TOTP). If the second step is not completed within 5 minutes, the password is asked again.
  • An escalating lock after 5 failed tries per user or 20 per IP address.
  • Open sessions are revoked at once when a password changes or access is removed.

Permissions

What a person can see and change
  • Role and business-unit scope is applied on every database query.
  • No one can approve their own request.
  • The agent is a user with its own role; it cannot sign in or approve its own request. · in build
  • Every step that reaches a customer waits for a person's approval. · in build

Data

How records are protected
  • Each company has its own installation and its own database.
  • Seven separate database roles: the app cannot change the schema or touch audit records.
  • The audit trail is chained and locked at the database level.
  • KVKK retention, erasure and data subject request flows.
  • Company names, contacts and contact details never reach the model; names become random codes. · in build

Continuity

If something is lost
  • An encrypted backup every 6 hours, in an account separate from production.
  • Backups are encrypted with a public key; the server cannot read old backups.
  • Target: at most 6 hours of data lost, working again within 4 hours.
  • Regular restore drills with recorded evidence.

Scenarios

What happens if something goes wrong?

A password is stolen

Sign-in fails without the second-step code. Guessing locks after 5 failed tries. Resetting the password closes every open session.

An employee tries to rewrite history

They can touch only the records their role allows. Not even the app itself can change audit records; if an old entry changes, the chain breaks and it shows.

The server is lost

Encrypted backups sit in an account separate from production. The target is to be working again within 4 hours, with at most 6 hours of data lost.

An agent makes a mistake

The agent works only through controlled actions and cannot approve its own request. Every step that reaches a customer waits for approval; internal follow-up tasks are logged under the agent's name. An admin stops the agent with one switch, which also closes its account.

The model provider has a breach

All that leaks is codes, rounded amounts and day counts: "[C-7KQ]'s quote: 120,000 TRY, unanswered for 9 days." The key to the codes stays in Nexus, and only while the run lasts.

The spending limit is reached

Each call is priced at its worst case before it is made. If the daily cap or the weekly allowance is used up, the agent does not run and the run is recorded in red.

Usage

AI usage is weekly and always visible.

The subscription is priced by the modules you choose, with one of three AI tiers on top. Each tier grants a weekly allowance that your team sees as a percentage. The allowance renews every Monday at 00:00.

Weekly AI usage62%
AI tier 2Renews Mon 00:00
Weekly AI usage86%
Usage is highRenews Mon 00:00
When the allowance runs outThe agent waits for the new week. Each call is priced before it is made, so spending never goes past the allowance.

We share module and tier prices in the demo, based on the scope of your installation.

Demo

See Nexus on your own processes.

Share how your team is organised and what matters most. In the call we show the platform on your own processes and work out together where agents would save your team time.

  1. 1Needs and process assessment
  2. 2Platform walkthrough tailored to your company
  3. 3Installation scope and agent roadmap
Your details are used only for this request.