Platform Architecture

Overview

If you’re managing your own Kinetic environment, it helps to know what each part of the system does. Think of the platform as a collection of building blocks—each with its own job. Here’s a friendly breakdown of those components, what role they play, and why they’re important.

Core Services: Where Your Data Lives and Moves

Core

Think of Core as the central brain of your Kinetic Platform.
Responsible for:

Logging users in
Handling form submissions
Storing data securely

Anytime someone fills out a form, Core is where that data is first captured. It’s also where you define your forms and the basic structure of your apps.

Task

This is the "action engine" of the platform.
Once a form is submitted, Task decides what happens next:

Should an approval email be sent?
Should data go to another system?
Should a follow-up task be triggered?

You build those rules, and Task makes them happen.

Integrator

Integrator is the connector between Kinetic and the rest of your tech stack.
It talks to external tools like:

ServiceNow
Active Directory
Slack
Or any system with an API

You use Integrator to push and pull data, so everything stays in sync.

Orchestration & Administrative Consoles

System Coordinator

The behind-the-scenes organizer.
Manages:

New environment (tenant) setup
Connections to external systems
Certificates and platform resources

System Console

Your platform-level control panel.
Where system admins:

Create tenants
Manage back-end connections
Rotate security certificates

Space Console

The workspace for specific teams or departments.
Admins use it to:

Build forms and workflows
Set up integrations
Manage access controls

OAS Console

Your interactive API playbook.
This is where developers can explore and test the Kinetic API.

Front-End Code (Portals)

What your users see and interact with.
Formerly called “bundles,” this is the branded, user-friendly interface for forms, dashboards, and requests.

Search, Logging & External Data Helpers

Indexer

Indexer helps you find things—fast.
It powers search across your submissions, forms, and more.

Loghub

Your eyes into system logs.
It makes logs available in the Space Console for debugging and audits.

LogCollector

The backstage pass for logs.
Pulls logs from each service and sends them to Elasticsearch.

Agent

The bridge to external data.
Enables forms to pull live data from other systems—like fetching department lists from your HR tool.

Underlying Technologies (Supporting Cast)

Cassandra
A high-performance NoSQL database for storing large volumes of structured and unstructured data.
Elasticsearch
A powerful engine for indexing and fast search.
Filebeat
A tool that collects and ships logs to Elasticsearch for monitoring.
Docker
Ensures each component is packaged in a container that behaves the same in every environment.
Kubernetes
Orchestrates containers to keep everything running, scaled, and fault-tolerant.

What This Means for You

If you’re managing your own Kinetic install, you’re in control—but that also means:

You configure integrations (via Integrator)
You deploy updates and maintain container services (via Docker + Kubernetes)
You manage logs (via Elasticsearch + Filebeat)
You keep your systems secure (via System Console + System Coordinator)

But the good news? Each component has a clear purpose, and once it’s set up, the platform is designed to run reliably and scale with your needs.

Authentication & Authorization

The Kinetic Platform uses industry-standard methods to protect access and manage permissions. This ensures secure and flexible user access across environments.

Authentication

Authentication is managed by Spring Security within the Core service. When users attempt to access protected areas of the platform, they are redirected to the configured Identity Provider (IDP) for login. After a successful login:

A user profile is created or updated in Kinetic
Tenant-defined attributes help assign access and identity within the platform

SSO is supported out of the box.
We offer configuration guides for popular identity providers:

Authorization

The platform uses Attribute-Based Access Control (ABAC) to determine what users can and cannot do. Permissions are set based on:

User roles and attributes (e.g., department, team)
Resource attributes (e.g., form type, submission status)
Environment-specific conditions

These policies determine access to forms, submissions, workflows, and other platform elements.

Learn more:

External Integrations

While the Kinetic Platform is fully capable on its own, its power multiplies when connected to your existing systems.

Integrator Service

This service allows you to:

Define connections to tools like ServiceNow, Workday, AD, Jira, or custom APIs
Map and transform data between systems
Manage authentication and credentials separately from users

Whether you’re just starting or running complex enterprise integrations, we’ve got resources to help:

What’s Next?

Now that you understand the architecture, authentication, and integration pieces, you're ready to:

Configure your environment
Set up namespaces, tenants, and space-level settings
Deploy Kinetic into your Kubernetes or container-based infrastructure

Check out the Environment Setup Guide to begin your deployment journey.