From the screens people use (SSemForm) to files, workflows and AI agents — all on one platform. Install it on your own infrastructure; saga compensates failures automatically.
SSemWorks begins where SaaS automation tools stop — air-gapped networks, large-scale processing, transactional consistency.
From user-facing screens to the execution core, AI governance and large files — it is all in one platform, with nothing to assemble yourself.
Coordination, planning and execution run as separate layers on the Kafka message bus. A worker failure cannot stop the engine, and each layer scales horizontally.
When a microservice fails, the steps already executed are compensated automatically in reverse order. Progress is tracked on a dedicated console, and you can step in by hand.
Swap models freely across multiple LLM providers, and run agents that use tools. The MCP gateway federates many tools behind a single address and authorises down to the individual tool with an API key.
A dedicated file server takes the bytes while only a reference flows through the workflow. Load is separated in two places — on upload and between tasks — so files of hundreds of megabytes never weigh on your page servers or the engine.
Paste an existing n8n workflow JSON or a Make blueprint and it comes straight in. Service contracts, trigger semantics and expressions are compatible, so your team keeps its assets and its know-how.
Design with a drag-and-drop visual editor and monitor executions in real time. Folders, permissions, credentials and insights are managed on one screen.
A workflow begins and ends at a screen a person looks at. Build the forms and PDF templates yourself; signatures are bound to the submission and sealed as evidence.
Where a human decision is needed — approve, reject, request missing documents — the workflow pauses and waits. Once submitted, only the values you named flow onward.
Developers publish the microservices they build as packages, and each site's administrator picks and installs them from a settings screen. Nobody touches the server, and what is installed is usable on the canvas at once.
SSO over OIDC and SAML, LDAP/AD integration, two-factor authentication and role-based permissions. Even failed sign-ins are recorded in the audit trail, and secrets never are.
All inbound traffic through a single gateway, all execution on a distributed engine over the message bus — a simple principle holds the whole thing up.
Every external call must pass the API gateway before it can reach the engine. The engine plans the run and hands microservices to workers over the message bus, while state is always persisted in the data layer — restart any component and the record of the run survives.
From building a workflow to running and observing it — the whole cycle closes inside the platform.
Drag microservices together in the visual editor to compose a workflow. Existing n8n JSON and Make blueprints come straight in through Import.
Webhooks, schedules, messengers, SSemForm forms and more all pass the gateway and start a workflow.
Each microservice runs on a worker, in parallel and distributed, over the message bus. Large payloads bypass the bus automatically.
Track the whole run in real time; when a failure is detected, Saga rolls completed steps back in reverse order.
Built from standard technology your team already knows how to operate. No new stack to learn — your existing Java and container skills are enough to adopt it.
We will walk you through the right setup and rollout for your environment.
Get in touch