Nano · software infrastructure for institutions
Millions of people already use a conversational assistant on their phone. Nano enables an institution to distribute real software services there — persistent, secure and connected to data — without imposing another app and without depending on any one assistant.
For twenty years, offering a digital service meant building an interface, convincing the user to install it, creating an account — then hoping they would come back.
Assistants change that equation. The user already has the interface: they talk, in their language, from their phone. Nano brings what that conversation lacks to make it a real software service: identity, persistent data, rights, deadlines, reminders and business rules.
The assistant stays the interface.
Nano carries the service.
You choose the population and the service. You can fund access, bundle it with a contract, a loan or a membership. Nano operates the service. The user chooses their compatible assistant — or the Nano app, which carries its own.
The service belongs neither to ChatGPT, nor to Claude, nor to any other assistant. Data and rules stay with Nano; the channel can change.
These needs do not always justify a dedicated app. They do justify software.
Financed asset
A driver tracks mileage, expenses, maintenance and deadlines for the financed vehicle. The institution measures usage before assessing any effect on the quality of its portfolio.
Microfinance · mobilityPrevention
They keep their vehicle’s details and receive a reminder before a service, an inspection or the contract’s renewal date.
Insurance · garage networkObligations
A fisherman, a tradesperson or a farmer finds, in their language, the administrative obligations they only meet a few times a year.
Cooperative · public programme · NGOAccount, authentication, rights, languages, calendars, currencies, reminders and security are not rebuilt for every need.
Vehicles, mileage, expenses, servicing and deadlines.
Everything that must be done, renewed or paid by a given date.
A professional’s diagnostic tree, played step by step. The first product from an outside supplier: they keep ownership of their know-how, Nano distributes it. Restricted to its testers.
A new business service can join the same core without rebuilding the whole infrastructure — whether it comes from Nano or from a third party.
The assistant understands the request. The Nano server decides what is allowed, keeps the data and applies the rules.
Understands, explains and calls the tools the user is entitled to. In the Nano app, it is a small open model, interchangeable, hosted in Europe.
Authenticates, authorises, computes, keeps and logs the service.
Prices, subscriptions, codes and opening a country stay out of the assistants’ reach.
The presentation changes with the user. Storage stays based on international standards. Opening a territory becomes mainly a matter of localisation and validation.
No big bang, no heavy IT integration up front. A pilot measures real usage before any major industrial commitment.
Nano relies in particular on MCP and OAuth 2.1. The infrastructure is hosted in France. We systematically distinguish what is live, in progress and planned. Status as of 4 October 2026.
Pilot programmes
We work with institutions that already know their beneficiaries and have their trust. If you have identified a population, a country and a concrete need, we can start there.