# Cyoda

cyoda.com is the enterprise/commercial site for Cyoda.
It describes Enterprise Cyoda: commercially supported, scalable deployment of the Cyoda EDBMS
for regulated, mission-critical, and operationally complex environments.

## What Cyoda Is

Cyoda is an EDBMS — Entity Database Management System — that unifies transactional storage,
event-driven processing, and workflow orchestration in a single consistency architecture.

State, workflow, transactions, events, history, and business logic are unified in one architecture.
No separate orchestration layer. No separate audit service. No consistency seams to manage.

Core capabilities:
- Serializable Snapshot Isolation across asynchronous distributed workflows
- Immutable state history: every entity state transition is a durable, queryable event
- Point-in-time entity queries — not time-limited like Snowflake time-travel
- Durable retry for external API calls modelled as entity state transitions
- Workflow and state machine enforcement built into the storage layer
- Deploys on PostgreSQL (default), Cassandra (scale-out), or as managed service (Cyoda Cloud — coming soon)

## Cyoda Web Estate

- cyoda.com — Enterprise Cyoda. Commercially supported, scalable deployment for regulated and mission-critical environments.
- cyoda.dev — Open-source Cyoda. Developer-first, self-hosted, run-it-yourself.
- cyoda.com/cloud — Cyoda Cloud. Fully managed Cyoda platform, coming soon. Join the waitlist.
- docs.cyoda.net — Documentation and API reference.

## Markdown versions

Every page on cyoda.com is also available as plain markdown: append `.md` to
any page URL (e.g. https://cyoda.com/use-cases/loan-lifecycle.md). Blog posts
serve their original markdown source. The concatenated markdown of all core
pages is available at https://cyoda.com/llms-full.txt. A generated link index
of every page follows at the end of this file.

## Who It Is For

Enterprise Cyoda is for:
- System architects and engineering leaders in regulated industries
- Teams running stateful, auditable backend workflows at scale
- Organisations that need commercial support, SLAs, and enterprise engagement
- Financial services teams building loan origination, trade settlement, KYC, and agentic AI systems

## What It Replaces

Teams typically run Cyoda instead of: Postgres + Apache Kafka + Camunda/Temporal.
The glue code between those systems — and the partial-failure modes it introduces —
is eliminated when the same consistency model governs storage, events, and workflows.

## Enterprise Offering

Enterprise Cyoda adds:
- Support for audit-driven deployments: SLAs on workflow integrity, audit-trail validation,
  and temporal-history review
- Scalable operational modes: PostgreSQL and Cassandra, including migration between them
  without changing your entity model
- Regulated procurement and rollout: procurement paperwork, security questionnaires,
  implementation, and rollout support for regulated industries
- Long-term engineering engagement: roadmap access, co-engineering on high-consequence
  workflows, and direct contact with the Cyoda core team

## Company

Founded: 2012. Full-time: 2015, London.
First production deployment: 2017 (VC Trade, European private-debt market).
Previously deployed at a global KYC platform for four years.
Cloud offering: https://cyoda.com/cloud (coming soon — join the waitlist)

## Pages

- [Enterprise Cyoda: EDBMS for regulated production](https://cyoda.com/index.md): Build scalable, auditable backend systems on an integrated architecture. Enterprise Cyoda provides commercial support, procurement, and deployment for regulated production.
- [Blog | Cyoda](https://cyoda.com/blog.md): Technical articles on stateful systems, entity databases, and financial workflow engineering from the Cyoda team.
- [Support | Cyoda](https://cyoda.com/support.md): Get help with Cyoda — documentation, Discord community, and direct support for engineering teams building stateful systems.
- [For developers | Cyoda](https://cyoda.com/dev.md): Building with Cyoda? Start on the open-source project at cyoda.dev — the fully managed Cyoda Cloud is coming. Come to cyoda.com when you need commercial support.
- [For engineering leaders | Cyoda](https://cyoda.com/cto.md): The commercially supported EDBMS for stateful, auditable backend systems in regulated production. One consistency model for state, workflow, transactions, and history.
- [About | Cyoda](https://cyoda.com/about.md): Built by engineers who spent careers building the core regulated systems that run global investment banks. Cyoda reflects what financial systems actually need.
- [Use Cases | Cyoda](https://cyoda.com/use-cases.md): See how Cyoda powers loan lifecycle management, governed agentic workflows, governed claims adjudication, trade settlement, and KYC onboarding in financial services.
- [Corporate Loan Origination & Lifecycle | Cyoda](https://cyoda.com/use-cases/loan-lifecycle.md): Model corporate loan origination and lifecycle management as a Cyoda entity workflow with credit assessment, approval conditions, drawdown, servicing, and immutable history.
- [Trade Settlement & Regulatory Reporting | Cyoda](https://cyoda.com/use-cases/trade-settlement.md): Every trade state is a regulatory event. Cyoda gives you point-in-time reconstruction — no ETL pipeline or separate data warehouse required.
- [KYC & Customer Onboarding | Cyoda](https://cyoda.com/use-cases/kyc-onboarding.md): Model KYC and customer onboarding as a Cyoda entity workflow — STP, exception handling, EDD, ongoing monitoring, and immutable audit history in one consistency model.
- [Governed Agentic Workflows | Cyoda](https://cyoda.com/use-cases/governed-agentic-workflows.md): Use Cyoda to govern AI-driven business actions through entity workflows, traceable state transitions, audit history, and decision reconstruction.
- [Governed Claims Adjudication | Cyoda](https://cyoda.com/use-cases/governed-claims-adjudication.md): Use Cyoda to govern AI-assisted claims adjudication through entity workflows, traceable state transitions, audit history, adjuster review, payment, appeal, and reversal paths.
- [Contact | Cyoda](https://cyoda.com/contact.md): Talk to the Cyoda team about your use case.
- [Cyoda vs Temporal, Camunda, Kafka — Platform Comparison](https://cyoda.com/comparison.md): See how Cyoda's EDBMS compares to Temporal, Camunda, Confluent/Kafka, AxonIQ, and XTDB across the capabilities that matter in regulated financial services.
- [Cyoda Cloud — Coming Soon | Join the Waitlist](https://cyoda.com/cloud.md): The new Cyoda Cloud: a fully managed platform for regulated workflows. Prototype to production without re-architecting. Join the waitlist for early access.

## Optional

- [Cookie Policy (EU)](https://cyoda.com/cookie-policy.md): Learn about how Cyoda uses cookies and other related technologies on our website. This policy covers our cookie usage, your rights, and how to manage your preferences.
- [Privacy Policy](https://cyoda.com/privacy-policy.md): Learn about how Cyoda collects, uses, discloses, transfers, and stores your information. Our commitment to protecting your personal data and privacy rights.
- [Website Terms of Use](https://cyoda.com/terms-of-service.md): Terms of use for the cyoda.com website, operated by Cyoda Limited (UK). Covers acceptable use, intellectual property, disclaimers, and governing law.
- [A Technical Description of the Cyoda Platform](https://cyoda.com/blog/a-technical-description-of-the-cyoda-platform.md): This is a deep-dive technical reference for the Cyoda Platform (see https://cyoda.com), a distributed, transactional data-processing system built to support high-availability business applications. It outlines the architecture and mechanics of the Cyoda Platform Library (CPL), which includes asynchronous transactional workflows, point-in-time querying with snapshot isolation, distributed report execution, and event-context sharding. Designed for developers familiar with distributed systems, the document emphasizes low-level design decisions, like extended ACID semantics, integration with Cassandra and Zookeeper, and client-extensible workflows.
- [Entity Workflows for Event-Driven Architectures](https://cyoda.com/blog/entity-workflows-for-event-driven-architectures.md): dive into the details of *Entity Workflows* and show how an EDBMS naturally leads to a horizontally scalable event-driven architecture (EDA). The goal being to greatly simplify things, where the applications become “thin clients” of a platform
- [What’s an Entity Database?](https://cyoda.com/blog/whats-an-entity-database.md): An entity database is not just another way of storing rows and columns. It is designed around the concept of entities—real-world objects like customers, transactions, or devices—capturing their full lifecycle and every event that shapes them. Unlike traditional relational databases, entity databases maintain a complete, auditable history while still enabling real-time queries and complex workflows. This makes them ideal for businesses that need consistency, scalability, and transparency in handling data-intensive applications.
- [Cyoda vs. the Alternatives: A Platform Comparison for Technical Decision-Makers](https://cyoda.com/blog/cyoda-comparison-by-category.md): How Cyoda compares to workflow engines, databases, cloud-native orchestrators, and data platforms — and where it fits in your stack.
- [LLM’s Can Get You to a Demo Fast. In Fintech, After That It Gets Hard.](https://cyoda.com/blog/demo-to-poc-in-fintech.md): Vibe Coding can get you to a working MVP in a few weeks. But in fintech , the real test begins after the demo. This article explores why fast AI-generated builds often hit a wall when faced with real-world iteration, compliance, and due diligence and what semi-technical and non-technical founders need to put in place early to avoid painful rewrites later.
- [When Transactions Meet Workflows: Building Reliable Systems With Much Less Glue Code](https://cyoda.com/blog/when-transactions-meet-workflows.md): Most enterprises build reliable systems by stitching together databases, message brokers, and workflow engines. Cyoda offers a unified core where transactions, entity lifecycles, and point-in-time querying share one consistency model — so teams write less integration code and spend less time reconciling state across tools.