Govern automation across your security stack.
Automations run inside Kona on data from across your infrastructure, producing reports, visualisations, APIs and UIs governed end to end.
Some platforms automate. Some manage policy. Kona builds on top of both.
Tools like Tufin, AlgoSec and FireMon focus on policy across firewalls. Kona connects to those tools and to everything else in your environment, so your team can build automation that spans them.
SOAR platforms run incident response playbooks against security events. Kona is a development and runtime platform for any security automation: change workflows, recertification, custom dashboards, internal reporting tools.
Teams that try to build a governed automation platform in-house typically spend a year or more on infrastructure before delivering business value. Kona is that infrastructure, ready to use.
You write the business logic. The platform attaches the rest.
Anything you deploy on Kona — a script, a service, a dashboard — automatically inherits identity, permissions, audit, surfaces and tenant scoping from the platform. None of it has to be built per tool.
A Python script that queries your firewalls. A Go service that reconciles config. A TypeScript dashboard. Any language, any shape.
Identity, permissions, audit, surfaces, tenant scoping and secrets — inherited automatically the moment you deploy.
Users sign in once through your IdP. Sessions, refresh and logout are handled by the platform.
Fine-grained RBAC and per-user, per-endpoint rate limits enforced at the platform edge — before a request ever reaches your code.
Every UI click and API call is logged with full context. CSRF, XSS and injection protection follow OWASP defaults.
Define your logic once. Kona exposes it as a UI, a REST endpoint with auto-generated OpenAPI docs and an interactive editor, and to AI agents.
Users belong to one or many tenants. Data, branding and roles are scoped per tenant by the platform.
Enterprise-grade tables, forms, config editors and tenant-aware theming. Drop them into your app or skip the UI entirely.
What it actually looks like.
Self-hosted. Hardened.
Under your control.
Kona runs entirely inside your environment: on-premises or in your cloud tenant; fully air-gapped. Every request that crosses the platform is authenticated, authorised, and logged. The end systems behind Kona are never exposed directly.
On-premises, private cloud and air-gapped. Container-based deployment on Docker or Kubernetes. Your data residency, your operational standards, your existing disaster-recovery model. The licence applies across all your environments (development, staging, production), without paying twice for the same users.
SSO, fine-grained RBAC, multi-tenancy and audit are properties of the platform, not features you configure per tool. Every automation, report, dashboard or API built on Kona inherits them automatically. A colleague gets read-only policy access. An infrastructure team consumes an API. A compliance officer runs a report. Each sees exactly what they are authorised to see, and every action is recorded.
Workloads execute in isolated, containerised environments inside the platform's security perimeter — not on engineers' workstations. Credentials to firewalls, proxies and other infrastructure are stored centrally and injected at runtime; they are never embedded in scripts. Dependencies are managed through a multi-level supply-chain mitigation strategy: vulnerability scanning, pinning, review gates, controlled update cycles.
Kona runs on the signed images you hold, with no telemetry or third-party runtime calls. Standard deployments validate entitlement through a licence service; air-gapped environments operate under a separate agreement covering image custody. Source escrow arrangements are available on request for customers whose procurement process requires them.
Authenticated · Authorised · Logged · Self-hosted · Air-gapped capable
Building in-house: the scope is usually larger than it looks.
It starts with an HTML table. Then a dashboard, authentication, audit logging, API management, multi-tenancy. Platform work quickly outweighs the security work it supports. Kona is that foundation, ready to use.
Tap a segment to see its label
Platform effort stays minimal — just setup and routine updates. Engineering time goes into shipping security applications, and a steady stream of tools, dashboards and automations reaches the teams that need them.
Most of the timeline goes into building and maintaining the platform itself. Once the compliance audit lands, SSO, RBAC, audit trails and multi-tenancy have to be retrofitted on top — leaving almost no room for security work.
The pricing model, at a glance.
A base licence covers the full platform, professional services, and a starting number of users and tenants — across every deployment you run.
See what teams build on Kona.
Explore real use cases — from policy recertification to cross-system orchestration.