Scrydon

Introduction

Scrydon is a customer-deployed Enterprise Data & AI platform — deterministic workflows with agents inside, managed analytics, a typed ontology, and the governance to run them all where regulated organisations need them.

Scrydon is an Enterprise Data & AI platform that runs inside your own Kubernetes cluster — built for the Critical Digital Enterprise (banks, defence, public sector, and any team operating under ISO 27001 / 42001 / EU AI Act / GDPR / SOC 2 / SecNumCloud constraints). Through its unique Capability and DLP engine, external AI vendors are reached only when you opt in.

Three trust zones side by side: Scrydon the vendor on the left, your own Kubernetes cluster in the middle — ingress, the Scrydon services and an optional customer GPU namespace — and external vendors on the right. The accented arrow is the one piece of traffic Scrydon requires: a daily license heartbeat leaving the cluster for the license server, carrying no customer data. The blue arrows to cloud AI vendors and business systems only exist for integrations you install.

Want the hands-on tour? Skip ahead to Getting Started and build your first agent in 10 minutes.

How Scrydon thinks

Scrydon sits between classical RPA and Agentic AI — and offers both where each fits. Like N8N / Node-Red / UiPath, the backbone is a deterministic DAG: blocks run in topological layers, branches are pruned by typed Condition / Router blocks, and the execution graph is fixed at design time, not chosen at runtime by an LLM. But where a task genuinely needs autonomy — open-ended language work, classification, extraction — you drop in an agent as a typed block inside that graph. Deterministic by default, agentic where it earns its place. See Why deterministic.

Platform anatomy

Two extension axes — Scrydon ships the contracts, the ecosystem ships the implementations and presets.

Four stacked layers, each naming who builds it. Vertical packs — Fraude Intelligence, NATO Maritime, ISO Reviews, or your own — are built by customers and delivery partners and use the accented middle band: the capability surface Scrydon defines, covering blocks, triggers, tools, LLM, STT, TTS, OCR and embedding. That surface resolves down to horizontal vendor integrations, also built by customers and delivery partners, and the Scrydon platform runtime at the base provides the surface from inside your Kubernetes cluster.
LayerWho builds it
Platform runtime + capability contracts + first-party packsScrydon
Integrations and vertical packsCustomers + delivery partners (e.g. Delaware)
Vendor APIs (OpenAI, Microsoft, Salesforce, SAP, …)External — talked to, never extending the platform

What's in the box

Where to go next

Editing these docs

Every page links to its source on GitHub. Use Edit on GitHub in the "On this page" panel to propose a change, or Create documentation issue to report a problem — both are in the right-hand panel of every page.

On this page

On this page