Across enterprise software, the definition of a strong platform has shifted. It's no longer enough for a system to do its job well inside its own four walls. The platforms teams value most are open and extensible: they expose their data and their capabilities so that other systems, and increasingly AI assistants and agents, can build on top of them. Enterprises expect their tools to connect to the rest of their stack, to fit into the workflows they already run, and to be ready for a wave of AI-driven automation, rather than to sit off to the side as one more place to log in.
Physical security and IoT device management have been slower to make that shift, but the expectation is exactly the same. Security and IT teams want their device data and the actions they take on their fleet to live where the rest of their work already happens, in their dashboards, ticketing systems, automation, and AI tools. SecuriThings is built for that, and a set of updates makes the platform more open than ever.
Openness begins with the API. Historically, the SecuriThings API was mostly a way to read your fleet data. Now it does more: teams can also trigger the same remediation actions they run inside SecuriThings, such as restarting devices or rotating credentials, directly from their own tools, without logging into the platform at all. That means SecuriThings data and actions can flow into the systems a team already relies on: pulling fleet health into reporting, automating routine maintenance, or kicking off remediation from an existing ticketing workflow. The platform becomes a data and action layer other systems can build on, not a separate destination.
Open capabilities only matter if teams can actually put them to work. The enhanced Developer Center is designed to make that easy, and it's open to anyone, with no SecuriThings login required. It brings together clear documentation, real-world use cases, ready-to-run examples, and a live API reference teams can try directly from the page.
It also reflects how developers work today. Every page can be searched, or opened directly in an AI assistant like Claude or ChatGPT so a developer can ask questions about it in context. That's a small example of a larger idea running through this release: building on SecuriThings should feel modern, and it should work naturally with the AI tools teams already use.
The clearest expression of an open, AI-ready platform is the SecuriThings MCP Server, now in Early Access. MCP, the Model Context Protocol, is an emerging open standard that lets AI assistants connect to a system and act on it. With the SecuriThings MCP Server, a person can simply tell SecuriThings what they want in plain language, and get the answer inside an assistant like Claude, no code and no dashboard required.
This opens the platform to people who would never call an API directly: a security operations lead, an IT manager, or an executive who just wants a quick answer about the fleet. And it does so without giving up the controls that matter. Actions run in a person's own identity, with the same auditability, accountability, and safeguards as any action taken inside SecuriThings. It's a preview of where device management is heading: platforms that don't just hold your data, but let your people and your AI tools act on it, safely, from wherever they work.
The enhanced Developer Center is live now and open to anyone. To enable the API in your environment, or to learn more about the MCP Server Early Access, SecuriThings customers should reach out to their Customer Success Manager.