What is NuFi?
An AI platform built for organisations — your models, your budgets, your controls.
NuFi is an AI platform for teams and organisations. Think Claude, ChatGPT or Gemini, but with the models you choose, budgets you decide, one gate every request passes through, and a developer console for building on top.
If you have ever wished ChatGPT could use your company's preferred model, respect your team budgets, tell you what it said to whom, and let your developers call it from their own code with self-served keys, that is NuFi.
What you can do with NuFi
- Chat with the models your organisation offers. The gateway can front any provider with an OpenAI-compatible API, from OpenAI, Anthropic and Google to a model server on your own hardware. Which ones appear in the dropdown is your operator's decision, per deployment.
- Work with files and images. Drop PDFs, documents, code and screenshots into a conversation; the model reads them and answers in context.
- Build agents. No-code assistants with instructions, tools and knowledge files, shareable with a team. On by default on NuFi's hosted app; an operator can turn them off.
- Build flows and run agent teams. NuFi Studio is a canvas for pipelines you publish as endpoints; NuFi Works gives a team of agents a goal and an approval gate. Both open with the account you already have.
- Search the web and talk by voice, where the operator has enabled them.
- Connect from code. Self-service API keys from the console, each with its own budget and rate limit, on the same account.
Who NuFi is for
- Knowledge workers who want one AI workspace for research, writing, coding and analysis.
- Developers who want a modern model behind one key without juggling provider accounts.
- Admins responsible for AI adoption: who can use what, how much each team can spend, what every request was checked for.
What makes NuFi different
| Public AI products | NuFi | |
|---|---|---|
| Accounts | per-user SaaS | one organisation, your identity provider if you have one |
| Budgets | hidden in pricing | visible, per key and per user, set by you |
| Model choice | the vendor's | any provider, or your own hardware |
| Security checks | the vendor's, unseen | five controls at one gate, with a policy file you can read |
| Audit | none | every request traced with who, which model, what it cost |
| API access | separate billing | the same account, the same budget |
| Where it runs | the vendor's cloud | your host, or NuFi's |
The surfaces
| Surface | Where | Who |
|---|---|---|
| The NuFi app | chat.nufi.me | everyone |
| NuFi Console | console.nufi.me | developers, and anyone entering the agent products |
| NuFi Studio and NuFi Works | agents.nufi.me, which opens studio.nufi.me or works.nufi.me | builders and teams running agents |
| NuFi Admin Panel | admin.app.nufi.me | admins |
One sign-in. The app issues it, the console reads it, and the console vouches for you to Studio and Works. The admin panel keeps its own session against the same accounts.
Next steps
- Architecture: what runs where, and the two deployments behind the hostnames.
- Components: every service, in one table.
- Data flow: a single message, end to end.
- Security: the five checks at the gate.