{"id":42173,"date":"2026-06-17T09:44:51","date_gmt":"2026-06-17T07:44:51","guid":{"rendered":"https:\/\/smartfense.com\/?p=42173"},"modified":"2026-06-17T09:44:55","modified_gmt":"2026-06-17T07:44:55","slug":"why-we-integrate-via-api-not-an-agent","status":"publish","type":"post","link":"https:\/\/smartfense.com\/en\/blog\/why-we-integrate-via-api-not-an-agent\/","title":{"rendered":"Why we connect to your environment via API and not an agent on every device"},"content":{"rendered":"

When a security leader evaluates an awareness platform, one of the first technical questions is usually the most telling: what do we have to install? The answer says far more than it seems. It defines how long you will take to get started, how large your attack surface becomes, and how far the platform reaches inside your people\u2019s devices.<\/p>\n

At SMARTFENSE we made that decision long ago, and on purpose. We connect to your environment via API and open standards, without installing an agent on every device. It is worth explaining why, because that choice has concrete consequences for the security team and for every person in the organization.<\/p>\n

What does integrating via API instead of an agent mean?<\/h2>\n

An agent is a piece of software that gets installed and keeps running on every device in the organization. An API integration connects two systems that talk to each other through a defined interface, with no need to install anything on the user\u2019s device.<\/p>\n

For an awareness platform, that difference is fundamental. SMARTFENSE connects to the systems your organization already uses (the identity provider, the directory, the collaboration tools, the compliance console) and works from there. It does not need a process of its own living on each person\u2019s corporate device.<\/p>\n

Why did we choose to integrate via API?<\/h2>\n

There are four reasons, and none of them is incidental.<\/p>\n