AnantState
Integrations

It runs beside your systems.

AnantState reads events and reference data from the systems you already run. It only changes anything in them through named, recorded actions. Your existing systems stay the source of truth.

In plain termsIt sits beside your systems and reads from them. It does not replace them.

Getting events in

RouteUse when
StreamingYou have a live event stream and want entity state to advance in real time
REST sourceA system can push, or be polled, over HTTP
Scheduled pullA warehouse or batch system holds the history and latency is acceptable
File or bulk importBackfilling a population to stand up a new domain

Every route lands in the same place: events attributed to a domain, mapped to entities, converted into state updates. Ingest failures are retained in a dead-letter view with the reason, so a mapping bug shows up as a visible backlog rather than as missing data.

Every route lands as an event

  1. Streaming: A live stream; state advances in real timeLeads to: An event
  2. REST source: A system can push, or be polled, over HTTPLeads to: An event
  3. Scheduled pull: A warehouse or batch system holds the historyLeads to: An event
  4. File or bulk import: Backfilling a population for a new domainLeads to: An event
  5. An event: Attributed to a domain, mapped to an entityLeads to: State update; Dead-letter view (could not be mapped)
  6. State update
  7. Dead-letter view: What could not be mapped, with the reason
  8. Keyqueue: Where every route converges; cylinder: Stored state; external: Kept in view, not lost
However an event arrives, it ends up in the same place: attributed to a domain, mapped to an entity and turned into a state update. What cannot be mapped is kept in view, not lost.

What we already speak the language of

A catalog of vetted starting points.

Each preset pre-fills the connection editor with the transport, the auth model, the endpoint and pagination shape, and a suggested entity key. You still supply your instance URL, your credentials and the mapping to your own event schema. Every preset is one of two transports, a REST poll or a SQL source, which is why the list can grow without becoming a maintenance liability.

Available todaySystems
IT service managementServiceNow, Jira
CommerceShopify
IdentityOkta, and any OIDC-compatible provider
HR and workforceWorkday
DatabasesPostgres-compatible sources
PlannedSystemsWhy it is not a preset
Cloud data warehousesSnowflake, BigQuery, DatabricksThey need a SQL driver of their own: a real adapter, not a configuration
REST vendors with header-based cursorsFor example SalesforceThey need a link-following paginator the generic REST source does not yet have

We publish the distinction rather than blurring it. A marketplace that lists a planned connector beside a working one is how an integration project starts with a surprise. A connector is a convenience, not a prerequisite: if a system can emit an event or answer an HTTP call, it can feed a domain without waiting for us.

How the platform acts: nothing happens without an actor

RouteNotes
Recommended action, human-approvedThe default posture. The platform ranks, prices and explains; a person decides.
Auto-applied action, where you grant authorityPer action class, within limits and budgets, fully attributed, and halted when evidence conflicts.
NotificationAlerting into the channels your teams already use.
ExportEntity and alert exports for the systems that still need a file.

Automation is never a single global switch. See next best action.

How the platform acts: nothing happens without an actor

  1. AnantState: Ranks, prices and explainsLeads to: Recommended action; Auto-applied action (if granted); Notification; Export
  2. Recommended action: A person decides. The default posture.
  3. Auto-applied action: Where you grant authority, per action class
  4. Notification: Into the channels your teams already use
  5. Export: Entity and alert files, for systems that need one
  6. Keyemphasis edge: The default path; dashed: Only where you grant it
By default the platform recommends and a person decides. Automation is granted per action class, within limits and budgets, and is halted when the evidence conflicts.

A new world is a definition

A domain definition declares:

  • entities and how to identify them
  • state dimensions, their bounds, and the primary dimension that carries business value
  • baseline dynamics: how state moves without a model
  • interventions available, with costs and modeled effects
  • the decision horizon the domain must be right at
  • the residual weight: how much the learned correction is trusted

Because it is data, a new industry world can be stood up and evaluated without changing the engine, and a definition can be versioned and reviewed like any other governed artifact.

The same engine, in front of many sources

A new world is a definition. The way events arrive changes; the engine does not.

A store, an account, a patient pathway and a turbine all have state. What differs is the world, and a world is data: the engine does not change.

Tell us what you would connect first

Name the system that holds the events. We will say whether it is a preset, a REST source or a bulk import, and what the mapping looks like.