Home / Platform

One agentic banking platform.

Agents for your staff and your customers, one control plane over all of them, and a private copy for your bank.

How it fits together.

Customers meet the advisor in your app. Staff work with agent teams in rooms. Every agent, on either side, sits under the same control plane and writes to the same record, inside a copy of Tuvel that belongs to your bank.

CustomersTuvel Advisor in your app
StaffAgent Teams in Rooms
99 agents on 14 desksLending, KYC, wealth, compliance, fraud, trade, service and more
One control planeLevels, limits, approvals, model routing, kill switch, audit
Your bank’s private copyYour brand, your connectors, your data handling

Six products.

Each one stands alone; together they share the agents, rooms and controls.

Why one platform.

What a bank gets when both doors run on the same controls.

  • Earned autonomy and one control plane

    Per-agent levels and results scores, budgets and model routing, customer-chosen autonomy inside bank caps, a kill switch on every agent and action-level audit.

  • Both doors

    A customer front door and staff agent teams on the same control plane and the same record.

  • Your private copy

    Deployed per bank, under your brand, with your models, connectors and data handling.

  • Alongside your systems

    Connects to core banking, loan, CRM and KYC systems through OpenAPI or MCP, without replacing them.

  • Multiplayer AI

    Agents work as departments, with a lead agent, hand-offs and shared rooms with your staff.

What makes Tuvel different

The console.

Where your team sets up agents, approves work and reads the record.

  • Agents and teams

    Every agent with a role, a level and a budget, organised as departments.

  • Skills

    Procedures your agents follow, each with a priority, so repeat work goes the way that worked.

  • Knowledge

    Your products, policies and circulars in one place every agent reads before it answers.

  • Approvals and inbox

    Everything waiting on a person, oldest first. Only the button approves.

  • Launch under your brand

    Your name and look. Agents go sandbox, staging, live, with checks at each step.

  • Connectors

    Your systems through OpenAPI or MCP, granted to one agent at a time.

  • Audit

    Every turn, tool call and decision, on a record your team can read.

Build your own agents.

Describe an agent in plain English in the console. The builder drafts it under the same controls as every other agent, and an admin puts it live. Available now

  1. Describe it in plain English

    In the console, say what the agent is for: the desk, the work, what it reads and what it may do.

  2. The builder asks

    Where the description leaves a gap, such as who approves or which system holds the data, the builder asks.

  3. A draft agent

    It drafts the agent: role, instructions, starting level, approvers and the tools it needs.

  4. Only the listed tools

    The agent is granted only the tools listed for it. A new tool grant waits for an admin.

  5. Sandbox, staging, live

    Automated checks run before each step, and only a bank admin puts the agent live.

Tuvel Launch.

Build more front doors on the same agents, under your brand, with checks before each one goes live.

  • Available now

    Launch

    Your name and look, the agents behind it, and sandbox, staging and live, with automated checks at each step.

  • Available now

    Tuvel Launch

    New front doors on the same agents, under the bank’s brand.

  • On the roadmap

    An RM assistant

    A front door for relationship managers, built with Launch.

  • On the roadmap

    A corporate client treasury assistant

    A front door for corporate treasurers, built with Launch.

  • On the roadmap

    A collections voice agent

    A voice front door for collections, built with Launch.

Deployment.

Deploy on Google Cloud, AWS or Azure, inside your bank’s private VPC, in the region you choose. A private copy per bank, with its own database and one fixed outbound IP address. Models are set per agent, including open-weight models hosted in India.

Deployment, models and data handling

Integrations.

Your core banking, loan, CRM, KYC, payment and document systems connect through OpenAPI or MCP, granted to one agent at a time, over mutual TLS, signed requests or OAuth. Where your core vendor offers MCP skills, Tuvel can use them directly.

How connectors work

Questions.

What is the Tuvel platform?

An agentic banking platform with six products: Tuvel Advisor for customers, Tuvel Agent Card for the payments the advisor makes, Tuvel Agent Teams for staff, Tuvel Rooms where staff and agents work a case together, Tuvel Control Plane over every agent, and Tuvel Launch for new front doors. Each bank gets its own private copy.

What is Tuvel Launch?

Launch builds new front doors on the same agents, under your bank’s name and look. Each one moves from sandbox to staging to live, with automated checks at each step, and only a bank admin puts it live.

Can we start with one product?

Yes. Each product stands alone, and together they share the agents, the rooms and the controls. Most banks start with one desk or one customer journey.

Can our team build its own agents?

Yes, in plain English in the console. The builder clarifies what it needs, drafts the agent and grants only the tools listed for it. The agent moves from sandbox to staging to live with automated checks, and only a bank admin puts it live.

Where does Tuvel run?

In a private copy for each bank, with its own database and one fixed outbound IP address the bank can allowlist, inside the bank’s private VPC on Google Cloud, AWS or Azure, in the region the bank chooses.

See it in 30 minutes.

A walkthrough with the people who built it, on the desk or journey you choose.

Book a 30-min walkthroughPick a time (opens the booking calendar in a new tab)

Or write to demo@tuvel.co.