Skip to content
ABOUT SECUNO · THE NETHERLANDS

Security was built for the giants. We build it for the ones who guard everyone else.

Secuno is a Dutch security platform for MSSPs and IT service providers: the teams that carry hundreds of client environments with a handful of engineers. We are small, we run on our own servers, and we intend to stand next to the biggest names in this industry without becoming them.

WHY THE SHIPS

A handful of ships. Not an armada.

On 1 April 1572 a small fleet sailed into Den Briel, and a town nobody expected to fall changed sides. It did not take a navy. It took a few ships, good timing and people who knew the water.

We like that story. In this market "a small Dutch vendor" is usually meant as a warning. We take it as a description, and as a plan.

Stef Leeman, director of Secuno, standing in the office
Stef LeemanDIRECTOR · SECUNO
The mission

Make the security of the biggest companies ordinary for everyone else.

The best protection has always gone to whoever could pay for a room full of analysts. We think that is the wrong way round. So we automate the work from detection to a verified fix, keep every client's data in the EU, and put the result in the hands of the MSPs who look after everyone else. That is how a small Dutch company intends to stand among the biggest names in security.

FOR
The people protecting many: MSSPs, IT service providers, and small teams running their own security.
AGAINST
Tools built for one enterprise and stretched over many clients with a portal.
FROM
The Netherlands, for customers anywhere in the world. Wherever you are, your data is hosted in the EU, on our own servers.
The manifesto

Six things we refuse to do

A company is easier to judge by what it will not do. Each line below links to the page that backs it up.

  1. We refuse to send your clients' data to someone else's AI.

    The AI engine runs on our own servers in the Netherlands. No inventory, CVE match or risk record goes to an outside AI provider.

    How we secure it
  2. We refuse to call a closed ticket a fix.

    A risk closes when the device inventory shows the patch, and reopens by itself when the vulnerability comes back.

    Vulnerability management
  3. We refuse to bolt multi-tenancy on afterwards.

    Partner, client and device were in the model from the first day. The database itself keeps one client's rows away from another's.

    The platform
  4. We refuse to call software a SOC.

    Software watches, correlates and acts inside the limits you set. A SOC is people. Today those people are yours, or your MSSP's. Our own staffed SOC is in preparation, and we will only call it one when analysts sit in it.

    Detection and response
  5. We refuse to show a logo wall we did not earn.

    No invented customer names and no round success numbers. References exist, and we share them under NDA.

    Ask for a reference
  6. We refuse to hide the price.

    Prices for single organisations are on the site. MSPs and enterprises get a quote, because their numbers differ, not because the price is a secret.

    Pricing
Proof of pace

55 releases, every one written up in public

We cannot show you twenty years of history. We can show you the 9 months our release notes cover. Each square is one release with public notes: what was added, what was fixed and what changed.

PlatformWindows agentCounted from the release notes on this site.
An honest ledger

What the big names bring, and what we bring instead

You should know what you give up by choosing a young company, and what you get for it.

A large vendor usually hasWe have

A wall of customer logos.

References under NDA, and not one invented name.

Offices on three continents.

One home base in the Netherlands, built for customers anywhere. Your data stays in the EU.

A roadmap you hear about in a sales call.

A public roadmap and public release notes.

A partner portal on top of a single-tenant product.

Multi-tenancy enforced by the database itself.

A cloud AI behind the features.

Our own AI on our own servers.

Who we build with

Shaped by the operators who run it

Secuno is shaped with early design partners running it against real environments. The three profiles below are representative use cases, not named customers.

Multi-tenant MSSPs

Running Secuno across real client portfolios, from agent rollout to board-level reporting, in a single instance.

Regulated SMBs

Healthcare and finance organisations evidencing NIS2 and ISO 27001 obligations continuously, without a dedicated analyst.

Internal IT teams

Teams managing several entities that needed real multi-tenancy and an automated loop from detection to fix, not another scanner.

06:00 · DAYBREAK

Come and see what a small fleet can do.

We deploy the agent together, run the first correlation and show you your own risk position. No slides, no generic demo.