Bastino lives on every Fisher Platform screen. Ask it, request it or say it out loud, and it will search, summarize, hand you the Excel, read the contract and make the change. With your permissions, with your confirmation and with your data in your instance.
documentos_listar file 7 7 pending · 0.2 sdocumento_leer Tax status certificate verified citations7 documents are missing; the mandatory ones:
| Requirement | Status |
|---|---|
| Letter of commission · import | Missing |
| Program annex I | Missing |
| Program annex II | Missing |
The certificate is dated 10/10/2026 and the RFC matches the record [cite p. 1].
Real screenshots of the platform in a demo environment, with fictitious data.
With access to everything you can see in Fisher Platform, and to the same actions you would take on screen.
"What is due this week?", "what do we owe this supplier?", "how are Purchasing and Warehouse related?" It answers with tables linked to each record.
Issue and send an invoice, record a payment, assign a ticket, rule on a requirement, approve a purchase, move a candidate, record a stage of a procedure… with the same logic as the screen.
Excel, Word and PowerPoint files ready to download in the chat itself, diagrams and tables that copy as they are.
A contract, a certificate, the PDF you attach: it reads it and every claim carries its citation, checked on the server against the document.
Dictate in Spanish or English and listen to the answer, or talk with it as on a call while you walk the plant.
"Every Monday, send me what is due" or "when an urgent ticket comes in, alert me on WhatsApp": scheduled and event-driven tasks, with your permissions.
One expert in collections, another in foreign trade: agents with their own instructions and tools, which can never do more than whoever asks them.
Your customer asks about their invoices or their file, your supplier about their payments and your employee about their vacation. Each sees only their own.
It queries your other systems over MCP, and Claude, ChatGPT or Copilot can query Fisher Platform through Bastino, as the person connecting.
An AI that acts inside your ERP has to be, first of all, predictable. This is how Bastino is built.
Each customer has its own database, files and keys. Bastino's conversations, memory and audit live there, not in a separate service.
Claude, OpenAI, Gemini or Azure OpenAI with your own key, or a model of your own (Ollama, LM Studio, vLLM) inside your network: then the conversation never leaves your company.
Each tool checks your permissions and your screen access. If you can't see it, neither can Bastino. In the portals, each person sees only their own company's data.
Every change goes through a card with the before and after, in red if it deletes or touches sensitive fields, and is confirmed only once even if you press twice.
Installing modules, granting itself permissions, lowering security, deleting backups or disabling its own user are out of its reach, and cannot be enabled from any setting.
What third parties write —a ticket subject, a document, a response from another system— travels flagged as untrusted data, and links are filtered before being shown.
It is not a setting that an administrator or an instruction hidden in a document can switch on: what doesn't exist can't be requested. A module can add exclusions, never remove them.
In honesty: no AI is infallible against malicious text. That is why Bastino doesn't depend on the model "behaving": the critical doesn't exist, what is protected is rejected by the server and everything else goes through your confirmation. The model may make mistakes; your ERP doesn't change without you.
It is configured in Settings, per installation, and changed without touching anything else.
From Anthropic, with your own key.
OpenAI directly or Azure OpenAI on your own subscription.
From Google, with your own key.
Ollama, LM Studio or vLLM on your network: nothing leaves your company.
No. It acts as the person asking: each tool checks that person's permissions and screen access. It has no credentials of its own and no administrator mode.
No. Reading is done on its own; any change is proposed on a card with the before and after of each field and is only applied when you press "Confirm". It can also be set to "read-only" for the whole company or per role.
Conversations, memory and audit stay in your instance, with its own database. Only what is needed to answer each question travels to the AI provider, using your company's key, so that provider's terms apply; with your own model inside your network nothing leaves.
What third parties write travels flagged as data, not as an order. And even if the model got confused, critical actions don't exist and every change goes through your confirmation, in red if it is sensitive.
Bastino comes included in Fisher Platform. Model usage is paid by each company with its own key, and you can set budgets per person, role or door so it never gets out of hand.
Yes. Bastino is an MCP server with OAuth 2.1: the person authorizes the connection with their session, and from outside it can query with their permissions. Changes are never applied from outside; they stay proposed until confirmed in Fisher Platform.
We show you Bastino with your modules, your AI provider and your permissions, and how your IT team governs it.
The screenshots are from a demo environment with fictitious companies and people; no data corresponds to a real customer. The data-use terms of each AI provider are those the provider publishes for its API; Fisher Networks does not send data to any provider on its own.