Skip to content

Product

A company memory and named agents, inside the tools you already use.

cleverpod is not another chat window. It is a set of agents with a name, a scope and rights, working from your company's own memory, in your business software, team channels, meetings and e-mail.

Company memory

Documents, conversations and decisions, indexed and retrievable.

  • Documents

    Contracts, procedures, reports, offers: indexed once, retrievable by meaning, with the source attached to every answer.

  • Conversations

    Channels, threads and meeting notes become part of the memory, so that context is not lost when people change.

  • Decisions

    Decisions are recorded with their date, their author and their reasoning, and can be found again when the question comes back.

  • Retrieval first

    Agents look up the memory before answering or acting. What the company does not know, they say they do not know.

Named agents

Each agent has a name, a role and its own rights. They work where the team works.

In your business software

Accounting, CRM and projects: prepare entries, reconcile, update opportunities, draft follow-ups, keep tasks current. Deep integration with Odoo, accounting included.

In team channels

Channels and rooms: answer from the memory, summarise threads, prepare the next step, ask for approval where needed.

In meetings

Minute-taker: attendance, decisions, actions and owners, written up and filed in the memory.

In e-mail

Read, classify and draft; nothing is sent without a human validation.

Secrets vault

Agents use accesses without ever seeing the values.

  • References, not values

    An agent asks for an access by name; the platform performs the authentication. The value never enters a prompt, a log or a transcript.

  • Scoped grants

    Each agent is granted specific accesses, for specific verbs, revocable at any time.

  • Auditable use

    Every use of an access is journaled: which agent, which access, for which action.

Driven web navigation

An agent executes authorised web journeys.

  • Authorised journeys

    Orders, invoice downloads, searches: each journey is defined and scoped in advance on given sites.

  • Accesses from the vault

    Logins are performed from the vault; the agent never handles a password.

  • Approval before effect

    Placing an order or confirming a payment waits for a human decision.

Governance

Agents only act within their rights, and only after approval.

  • Rights per agent, per verb

    Read, draft, propose, act: each agent is granted verbs on given scopes, and nothing else.

  • Approval before any effect

    Publishing, paying, sending: the request waits for a human decision, recorded next to the action.

  • A journal of everything

    Who asked, which agent, which access, which action, who approved, what happened: kept and searchable.

  • The details

    Principles, hosting and commitments are described on the Security and governance page.

Deployed as pods

cleverpod is not one large application but a set of independent services, the pods, each responsible for one capability.

One pod, one capability

Memory, agents, vault, web navigation, mail, meetings: each pod runs on its own, with its own scope and rights.

Start small, extend later

You begin with the pods your team needs. Adding one later, or removing one, does not touch the others.

A single governance

Every pod answers to the same approval circuit and writes to the same journal. No capability sits outside governance.

Want to see it on your own tools?

Tell us which business tools, channels and mailboxes your team uses; we come back with a proposal.