Security

What runs where,
and who can reach it.

How Kantrix keeps your sites, your data and your access secure. Our security overview answers the full vendor questionnaire.

Request the security overview Report a vulnerability
01How it's built

Your workloads stay on your nodes.

Kantrix has two parts. Node software runs on hardware you control. A control plane runs the portal. Every connection between them starts at the node.

At your site Your nodes
  • Virtual machine and container disks
  • Your workloads and the data in them
  • No inbound ports open to the internet
Run by Kantrix The control plane
  • The portal and sign-in
  • Records of your sites, nodes and workloads
  • Console and shell sessions you open in the portal, passed through

Kantrix Sovereign runs the control plane on your own hardware instead, with no outbound connection. Compare the versions.

02Where data is

Every location, named.

Kantrix Cloud runs on Amazon Web Services.

WhatWhere
VM and container disks, and the data in themYour nodes, at your sites
Portal, database, sign-in and emailAmazon Web Services
Stored credentials and VM loginsEncrypted with AWS Key Management Service
Questions typed into the portal's assistantAmazon Bedrock. Conversations are stored
kantrix.io and status.kantrix.ioAWS, US East (N. Virginia)
03Access

Each person sees what their role allows.

Roles checked by the server

Every request is checked against the person's role and the clients and sites they're scoped to.

Authenticator apps and passkeys

Any user can add a second step to sign-in, with an authenticator app or a passkey.

API tokens that expire

A token never has more access than the person who made it, and always expires: after 90 days by default, a year at most.

An audit trail no one can change

Every change is recorded with who made it, when and their role. No one can edit or delete it, not even us.

Credentials encrypted

Credentials for connected services, and generated VM logins, are encrypted with AWS Key Management Service.

No staff shell on your nodes

Kantrix staff cannot open a console or shell on your devices.

04Nodes and releases

Checked before it reaches your hardware.

A signed installer

The installer checks the image's signature and checksum before it writes to any disk.

Locked local accounts

On an installed node, the root and admin accounts are locked. Signing in at the console needs portal credentials.

Nothing to open

A node needs no inbound connection from the internet. On your network, it listens only on the ports in our site checklist.

Tested before every release

Tests run on every change, and again in the release build, before anything is published.

Releases that can't change

Each release pins exact image digests, and published images can't be overwritten.

Watched every minute

A checker in a second AWS region tests the portal every minute. status.kantrix.io

05The security overview

The full answers, in writing.

Our security overview answers more than 60 vendor review questions, and we update it with each release.

1Hosting and data location
2Encryption
3Identity and access
4Separation between customers
5Kantrix staff access
6 to 11Logging, backups, vulnerabilities, incidents, releases and node software
Request the security overview
Who runs your IT?
06Questions

About security.

Can Kantrix staff see my data?

Our platform staff can see your inventory in the portal: sites, nodes and workloads. They can't see inside your VM disks, and they can't open a console or shell on your devices.

Can I keep my backup product?

Yes. Run the backup product you trust inside each VM. Your partner can set it up.

What happens if the control plane is unreachable?

VMs on replicated storage keep running.

Report a vulnerability

Found something? Tell us first.

Email security@kantrix.io with what you found and how to reproduce it.

Email security@kantrix.io Request the security overview