Obot now has a partner in Japan. Pentio, a Tokyo-based identity and security integrator, is bringing Obot to Japanese enterprises, with implementation, training, and first-line support delivered in Japanese. Pentio announced the partnership today, and Obot is available in Japan through them starting now.
This is a big deal for us. Japan has some of the most security-conscious IT organizations in the world, and the teams I have met there are moving fast on AI agents. They want to give developers and employees access to tools like Claude Code, Codex, and Cursor. They also want to know exactly which systems those agents can touch, who approved it, and what happened. That is the problem Obot solves, and Pentio is the right company to deliver it in Japan.
Who Pentio is
Pentio was founded in Tokyo in 1998 and has spent years helping Japanese companies control identity and devices. They sell and support OneLogin for workforce identity, SecureW2 for device trust and certificate-based access, and Sumo Logic, Stellar Cyber, and Safeguard on the security side. If you are a Japanese enterprise doing zero trust seriously, there is a good chance Pentio has been in the room.
The way Pentio describes it, they have covered who the person is and what device they are on. Obot adds the third piece: what the AI agent is allowed to do. That framing is exactly right. An agent running on an employee’s laptop is a new kind of actor on the network, and it needs the same discipline as a user or a device. Pentio already knows how to design identity integrations, access policy, and rollout plans for cautious enterprise buyers. Adding agent control on top of that is a natural extension of what they do.
“For many years, Pentio has helped Japanese enterprises control who is accessing their systems and from which device, through OneLogin and SecureW2. AI agents are now the third actor on the network, alongside people and devices. With Obot, our customers can apply the same level of control to AI agents: approval, permissions, and a complete record of every action. We are delighted to bring Obot to customers in Japan, with end-to-end support from deployment design through Japanese-language support.”
Every enterprise I talk to is working through the same sequence. Developers start using AI coding agents. Those agents want access to GitHub, Jira, internal APIs, databases, and SaaS tools. Someone wires up an MCP server or pastes in an API key to make it work. Within a few months the company has dozens of agents and hundreds of integrations that nobody approved and nobody can see.
Pentio’s announcement names the three problems that follow, and I could not have put them better. OAuth sprawl, where agents hold permissions that are never revoked. No visibility into what an agent did through which tool. And shadow MCP, where employees run MCP servers with personal credentials and company data flows to outside APIs that IT has never heard of. Agents act with a user’s credentials, but they have no judgment about which permissions are risky. Without controls, the security team’s only option is to stop AI adoption. Nobody wants that.
Japanese enterprises are hitting this moment right now, and they tend to approach it with more rigor than most. Security and compliance teams there expect clear policy, clean audit trails, and a known vendor on the hook for support. They also expect to work in Japanese, with a partner who understands how Japanese companies evaluate, procure, and roll out infrastructure.
We can build the product from California. We cannot do the rest from California. That is why we went looking for a partner rather than trying to sell direct, and why we picked a company whose whole business is identity and access rather than a general IT reseller.
What Pentio delivers
Pentio is a full-service partner for Obot in Japan, not just a reseller. Their team handles the whole lifecycle in Japanese, and Obot stands behind them for anything that needs engineering.
Licensing for both Obot editions: Obot Cloud, hosted by us, and Obot Enterprise, self-hosted in the customer’s own environment. Both are priced per user with no user cap, and both include Obot Sentry for unlimited devices.
Implementation consulting that starts with a requirements session, a free trial or PoC, and then moves to deployment and ongoing operations.
Design work where it matters: integration with the customer’s existing IdP (Entra ID, Okta, Google, OneLogin, and others), MCP catalog and access policy design, and Kubernetes or Docker environment build-out for self-hosted deployments.
Administrator training, onsite or online.
First-line support in Japanese, with escalation to the Obot engineering team in English when a product issue needs us.
The OneLogin piece is worth calling out. Pentio is one of the leading OneLogin partners in Japan, and OneLogin support for Obot SSO is coming soon. For companies already running OneLogin through Pentio, adding agent governance means working with the same partner who set up their identity in the first place.
Obot is open source, so you can also pull the code and run it yourself today. But if you want a team on the ground who will design the rollout with you, train your admins, and pick up the phone in Japanese, that team is now Pentio.
