Para empresas que querem crescer com controle

Um sistema para operar sua empresa com IA.

Vendas, marketing, atendimento, operação, financeiro e inteligência trabalhando sobre o mesmo contexto — para sua empresa ganhar escala sem perder controle.

Sua empresa inteira. Uma operação. IA trabalhando.

Ver a Centriu funcionando

Para empresas de qualquer setor que querem crescer com estrutura, controle e inteligência.

Representação ilustrativa do trabalho em execução

O problema

Sua empresa não deveria operar em pedaços

Não é falta de ferramenta. É que cada ferramenta resolve um pedaço, e ninguém é dono do todo. O custo disso não aparece numa fatura — aparece no mês seguinte.

Sistemas que não se falam
O mesmo dado é digitado de novo — e cada cópia conta uma história diferente.
Dados duplicados
Ninguém sabe qual versão é a verdadeira na hora de decidir.
Conversas perdidas
O cliente repete o contexto a cada canal e a cada pessoa.
Tarefas espalhadas
O trabalho vive em planilhas, mensagens e na memória de alguém.
Decisões sem contexto
A escolha é feita com o recorte que estava à mão, não com o que importava.
Automações desconectadas
Cada ferramenta automatiza um pedaço e ninguém enxerga o todo.

Nenhum desses problemas se resolve comprando mais um software. Eles se resolvem quando a operação inteira passa a trabalhar sobre o mesmo contexto.

A resposta

Tudo trabalha sobre o mesmo contexto.

A Centriu não é uma coleção de produtos. É uma plataforma em que clientes, áreas e agentes leem e escrevem no mesmo lugar.

Cliente 360

Um contexto, não vários cadastros

Cada conversa, tarefa, campanha, cobrança e decisão fica ligada ao cliente e à operação — não a um sistema isolado.

Clientes
Comercial
Atendimento
Operação
Financeiro
Marketing
Inteligência
Agentes
Consultoria

As áreas abaixo são partes da mesma operação, não produtos separados. Elas compartilham conta, permissões e histórico.

IA que trabalha — não um chatbot ao lado

A inteligência artificial da Centriu participa da operação: entende contexto, prepara trabalho, executa rotinas e pede aprovação quando importa.

Entende o contexto

Lê a operação, o cliente e o histórico antes de propor qualquer coisa.

Prepara o trabalho

Redige, organiza, calcula e deixa pronto para revisão humana.

Executa rotinas

Roda o que é repetitivo dentro dos limites definidos pela empresa.

Recomenda a próxima ação

Cruza áreas, identifica prioridade e mostra o motivo da recomendação.

Pede aprovação

O que é sensível passa por uma pessoa antes de valer. Sem exceção silenciosa.

Mantém histórico e aprende

Registra o que aconteceu e usa o resultado para melhorar a próxima decisão.

O que a Centriu faz

Uma plataforma, várias frentes de trabalho. Tudo no mesmo contexto, com a IA participando do que dá para acelerar.

Comercial

CRM, pipeline, oportunidades, propostas, follow-up e automações.

Atendimento

WhatsApp, Instagram, Messenger, chat do site e e-mail no mesmo contexto.

Operação

Tarefas, responsáveis, prazos, aprovações, agenda e capacidade.

Financeiro

Contas, cobranças, caixa, fiscal, margem, IR, orçamento e inteligência econômica.

Marketing

Planejar, produzir, aprovar, publicar e medir conteúdo e campanhas.

Inteligência

Painéis, alertas, previsões, recomendações e leitura executiva.

Agentes

Rotinas executadas continuamente pela IA com controle e aprovação.

Consultoria

Diagnóstico, estratégia, transformação, acompanhamento e especialistas.

Para quem é

Para empresas que querem crescer — e crescer certo.

A Centriu faz sentido quando o volume aumenta e a estrutura precisa acompanhar. Não é sobre setor nem tamanho: é sobre a operação conseguir sustentar o próximo estágio.

As vendas crescem, mas o processo não acompanha.

As áreas trabalham separadas e o cliente sente.

A operação depende de pessoas específicas.

O financeiro ficou complexo e o caixa perde visibilidade.

O atendimento cresce em volume e em canais.

A IA entra sem contexto, controle ou histórico.

Se a empresa ainda não começou a crescer, a Centriu também ajuda a preparar a estrutura para o primeiro salto.

Ver a Centriu funcionando

Consultoria

Tecnologia sozinha não resolve uma operação mal desenhada.

A Centriu combina tecnologia, inteligência, método e acompanhamento. A consultoria diagnostica, desenha, implanta e acompanha — com evidências, não com apresentação.

Diagnóstico e imersão na operação

Estratégia e prioridades

Roadmap de transformação

Desenho da arquitetura operacional

Implantação conduzida

Acompanhamento com evidências

Benchmarking e leitura de mercado

Especialistas, rede e inteligência coletiva

A participação de especialistas depende da solução e do contrato. Não é um item incluído automaticamente em toda contratação, e não prometemos acompanhamento humano ilimitado.

Veja a Centriu funcionando na sua operação

Uma conversa para entender onde a sua operação perde tempo, dinheiro ou capacidade — e o que a Centriu faria primeiro.

Ver a Centriu funcionando

problema

AI Cost Budget and Gateway Enforcement Automation: A Limit That Actually Reaches the Request

A spending limit that only shows up on a dashboard after the money is gone is not a limit. It is a report. Centriu TrustOps checks budget limits when an AI request is being sent. The outcome has seven real forms. It can allow it silently. It can log an alert. It can ask for a written reason before it continues. It can hold it for a person to approve. It can change it to a cheaper, already-approved model. It can limit its output size. Or it can block it completely. Every scope the limit applies to — organization, department, project, agent, vendor, model and more — comes from the request's own ID on the server. It never comes from what the caller says. If the limit-check itself stops working, the request is not silently allowed. It is marked as not checked. This is on its own metric. So "could not check" is never confused with "nothing was hit."

Quero resolver isso

Why a budget dashboard is not the same thing as a budget control

Most AI cost tools answer one question well: how much did we spend. That is a report. A report arrives after the decision that produced the cost has already been made. A real control has to be there when the decision is still being made. This is the moment a specific request is about to be sent to a specific model. It has to be able to do something about it right there. It should not just log it for a dashboard someone checks next week. The gap between "we can see the spend" and "we can act on the spend" is exactly where AI costs run away from a team that thought it had a budget in place.

Most AI cost tools answer one question well: how much did we spend. That is a report. A report arrives after the decision that produced the cost has already been made. A real control has to be there when the decision is still being made. This is the moment a specific request is about to be sent to a specific model. It has to be able to do something about it right there. It should not just log it for a dashboard someone checks next week. The gap between "we can see the spend" and "we can act on the spend" is exactly where AI costs run away from a team that thought it had a budget in place.

Quero resolver isso

How Centriu TrustOps enforces a budget at the point of the request

Configured limits are checked for every AI request. This happens as part of the platform's own routing pipeline. The outcome takes one of seven real forms. Allow does nothing further. Alert records the event on the request's own timeline without stopping it. Require justification blocks the request until a cost reason of at least ten characters is provided. Require approval holds the request for a person to decide. Route to cheapest authorized swaps the model for a cheaper one. But it only uses one already approved for that situation. It runs through the exact same candidate-evaluation logic as normal routing. So sensitivity, purpose, environment and region rules still apply. If no approved substitute exists, the request goes to approval. It is not silently allowed through with the wrong model. Reduce output limit lowers the maximum output size. Suspend or block stop the request completely. Every one of these checks against eleven real scopes. These are organization, business unit, department, project, asset, agent, user, vendor, model, process and purpose. The value used for each scope comes from the request's own ID on the server side. It never comes from anything the request body itself says. This stops an easy way to pretend to be a smaller, less-restricted scope. A declared fail-safe controls what happens if the limit-check service itself stops working. The request is not blocked. This is because the AI gateway's own basic limits still apply on their own. But the step is clearly recorded as unavailable. A special metric counts how often that happens. The system is built so "we could not verify this" is never quietly read as "nothing was over the limit."

Ver como funciona

What is actually built today

Seven real enforcement behaviors are checked when a request is made: allow, alert, require justification (at least ten characters), require approval, route to the cheapest already-approved model, reduce the output limit, and suspend or block.
Model substitution uses the same candidate-evaluation logic as normal request routing. Sensitivity, purpose, environment and region rules are never ignored by a cost-driven swap.
A strict rule says a cost-driven change never happens silently without an approved alternative. If there is no valid substitute, the request goes to human approval instead.
Eleven real budget scopes: organization, business unit, department, project, asset, agent, user, vendor, model, process and purpose.
Scope values come from the request's own ID on the server. They never come from a value the calling request can set.
A parent-budget ceiling means child budgets cannot spend more in total. This is when hierarchy enforcement is turned on.
A declared fail-safe: if the limit-check service is not working, the request is not blocked (basic gateway limits still apply). But the step is marked unavailable and tracked on its own metric. This tells apart "could not verify" from "nothing was hit."
Price versioning: publishing a new price version closes the previous one from its start date forward. It does not re-calculate costs that have already been added up.

Conhecer os recursos

What changes operationally

The main change is that a budget stops being a number reviewed after it happens. It becomes a condition checked at the only time it can still change the outcome. This is when the request is being made. Overspend is caught by a step-by-step response instead of a monthly surprise. A rule like "prefer the cheaper model" is actually followed, not just stated. If the enforcement system itself fails, it is visible, not silently allowed. Centriu does not say how much this saves. It depends entirely on how many AI requests an organization has. It also depends on how strictly its budgets are set up.

The main change is that a budget stops being a number reviewed after it happens. It becomes a condition checked at the only time it can still change the outcome. This is when the request is being made. Overspend is caught by a step-by-step response instead of a monthly surprise. A rule like "prefer the cheaper model" is actually followed, not just stated. If the enforcement system itself fails, it is visible, not silently allowed. Centriu does not say how much this saves. It depends entirely on how many AI requests an organization has. It also depends on how strictly its budgets are set up.

Quero esses resultados

A project approaches its ceiling mid-month (example scenario, not a real client)

A project's AI budget is mostly used up. There are two weeks left in the period. A new request from that project would spend more than the set limit. The routing pipeline checks the budget scope. This comes from the request's own ID, not from what the calling service says. It finds the set behavior for this limit is route_to_cheapest_authorized.

The engine looks for a cheaper model already approved for this project's sensitivity level and purpose. One exists. The request uses it instead, at a lower cost. No one needs to step in. A different request later that day needs a feature only the more expensive model provides. No approved cheaper substitute exists for that specific case. So instead of silently changing to a model that cannot do the job, or silently allowing the expensive one through, the request is held for approval. A team lead reviews it. They approve it because of the specific need. Then it continues.

During the same week, the limit-check service itself has a short outage. Requests during that time are not blocked. The gateway's own basic limits still apply. But every one of them is marked as having had a budget check that could not be verified. The count is visible afterward. So nobody mistakes "we couldn't check" for "everything was fine."

A project approaches its ceiling mid-month (example scenario, not a real client)

Conversar sobre meu caso

How to start

Começar agora

Frequent questions

What actually happens when an AI request would exceed a configured limit?

One of seven real actions happens: the request is allowed with an alert logged, blocked until a written reason is given, held for human approval, sent to a cheaper already-approved model, limited in output size, or stopped completely.

Can a cost-driven model swap use a model that was never authorized for that context?

No. The change uses the same check as normal routing. So sensitivity, purpose, environment and region rules still apply. If there is no valid approved substitute, the request goes to approval instead.

Where does the budget scope — which department, which project — come from?

It comes from the request's own ID on the server side. It never comes from a value the calling request itself says.

What happens if the budget-limit check service goes down?

The request is not blocked because of that outage. The gateway's own basic limits still apply. But the check is clearly logged as unavailable and tracked on its own metric.

Can a child budget spend more than its parent budget allows in total?

Not when hierarchy enforcement is turned on. The total of child budgets is limited by the parent's total.

Does changing the price recalculate past costs?

No. A new price version applies from its own start date forward. Costs that have already been added up are never re-calculated.

What does Centriu TrustOps cost?

It is sold by subscription with a published starting price. Exact current values are on the main pricing page.

Ainda tenho dúvida

See how Centriu TrustOps enforces AI cost budgets

A spending limit that only shows up on a dashboard after the money is gone is not a limit. It is a report. Centriu TrustOps checks budget limits when an AI request is being sent. The outcome has seven real forms: allow it silently, log an alert, require a written reason before it continues, hold it for a person to approve, change it to a cheaper, already-approved model, limit its output size, or block it completely. Every scope the limit applies to — organization, department, project, agent, vendor, model and more — comes from the request's own ID on the server. It never comes from what the caller says. If the limit-check itself stops working, the request is not silently allowed. It is marked as not checked. This is on its own metric. So "could not check" is never confused with "nothing was hit."

Quero resolver isso