Company
Amelfi is built by DigitalAPI.ai — a team that lives at the boundary where enterprises connect software to software. Agents are the newest traffic on that boundary, and we build the one governed path they take to your tools.
What we believe
They decide what we build, what we claim, and what we say no to. When a feature request collides with one of these, the principle wins.
Guardrails that hold let teams move faster, not slower. When the boundary is trustworthy, security stops re-reviewing every server and developers stop waiting on tickets — the approved path becomes the quick one.
No invented metrics, no certifications we don't hold, no vague "enterprise-grade." Everything we ship comes with runnable proof — and what's still on the roadmap is labeled as roadmap, in writing.
Self-hosted isn't a tier — it's the design center. Policies, credentials, and audit records stay inside your perimeter. If it can't run without us, we built it wrong.
How we work
A note from the team
Enterprises have connected software to software for decades — but there was always a person in the loop: a developer who read the docs, requested the key, and answered for the integration. Agents remove that person. They discover capabilities at runtime, compose tools in ways nobody sketched on a whiteboard, and act at a speed no review cycle can match. The question stops being "should this developer get a key?" and becomes "what may this agent see, call, and carry — right now, in this environment?" That question can't be answered by a policy document. It has to be answered by infrastructure.
Our operating rule is simple: the governed path has to be easier than the ungoverned one. The moment the approved route means tickets and waiting, teams route around it — and sprawl wins by default. So we spend our weeks where that rule points: making the install boring, making policy readable, making every denial explain itself, and backing each of those claims with something you can run. And when we're wrong, we'd rather hear it in a working session with you than have you discover it in an incident channel.
— the Amelfi team at DigitalAPI.ai
The people
All three worked on the original Apigee API Gateway earlier in their careers. Since then, they have built API and cloud platforms and led enterprise programs. Amelfi applies that experience to a new operating problem. Companies need to control what agents can discover, access, and do through enterprise tools.
Founder & CEO
Bharath sets the company and product direction. After leading API programs for Fortune 100 companies, he now works with customers to define how agents should access enterprise tools and what security teams need before they approve that access.
CTO
Rajanish brings two decades of experience building API and cloud platforms, including at Google. He leads engineering across DigitalAPI.ai and sets the technical direction for Amelfi.
Chief AI Engineer
Subbu works on the runtime and product model behind Amelfi. He connects the registry, policy engine, credential broker, and audit trail into one operating path, with a focus on how each decision is enforced and explained.
Working with us
No gated PDFs, no qualification funnel. Read, talk, or build — we'll meet you at whichever step you choose.
Early design partners shape the roadmap. Bring one real boundary — an internal API, a private MCP server — and we prove the whole governed path on your infrastructure in 4–6 weeks: one allowed call, one denied call, one revocation.
Not a slideshow. A working session on where the gateway sits in your estate, what your identity provider and SIEM see, and what a pilot would actually take.
Questions, objections, a boundary you're not sure fits — write to us. We reply to every message, and "we don't do that yet" is an answer you'll actually get from us.
Next step
There's no sales layer between you and the team shipping the gateway. Bring your architecture, your objections, or just your questions.