01
Source
Acquire bounded data from approved providers. Every extract is scoped, rate-limited, and tied to the terms it arrived under.
Governed data operations
Every source,one dependable current.
Bring trusted source data into the products that depend on it, with a clear record of how it was acquired, verified, and delivered.
Ingestion topology
Bounded acquisition → governance gate → verified delivery- Open map data
- Places directories
- Licensed feeds
- Public registries
Governance gateScope · evidence · readiness
Staging verifiedDelivered to inboxApplied by consumer
LegendApproved sourcePolicy checkpointVerified channelApplied in product
Illustrative source classes are categories of provider, not named integrations or endorsements. Provider attribution and licence terms are tracked per connector.
Operating today
One governed Confluendo instance for early operators.
Platform directionIndependently provisioned, customer-isolated service instances.
How it works
Three movements, one accountable path.
02
Govern
Verify scope, evidence, and delivery readiness. Simulation runs first, and a failed gate stops the path.
03
Deliver
Hand a signed package to the consuming product's inbox. Consumer apply is never a silent write.
Source classes
Different origins, identical discipline.
Each class arrives with its own terms and failure modes. Every one walks the same governed path, so its obligations travel with the data instead of living in someone's head.
These are provider categories, not named integrations or endorsements.
Open map data
Community-maintained geography and points of interest.
share-alike · attributedGeospatial reference
Administrative boundaries, postcodes, gazetteers, and coordinate frames.
reference · versionedPlaces directories
Venue and business listings with defined scope and coverage.
scoped · rate-boundedLicensed feeds
Contracted provider data with negotiated terms and refresh cadence.
contracted · terms-trackedPublic registries
Official company, property, transport, and regulatory registers.
official · evidencedOperational signals
Timetables, availability, pricing, and other fast-moving feeds.
time-boxed · perishableFirst-party uploads
Customer-supplied files and internal extracts on the same governed path.
owned · consent-trackedDocument extraction
Structured records derived from published documents and filings.
derived · provenance-linkedLifecycle
Nothing skips a stage.
Each batch walks the same path, and each step leaves a record. Operators approve the boundaries; the platform performs the bounded work.
- 01Automatic
Acquired
A bounded extract arrives with its terms, scope, and source record.
- 02Automatic
Simulated
A dry run proves the shape before any product data is written.
- 03Approval gate
Staging verified
A bounded staging write is checked against the declared expectation.
- 04Approval gate
Packaged
A checksummed delivery package is assembled for a named consumer.
- 05Recorded
Delivered to inbox
The package waits safely in the consuming product's inbox.
- 06Consumer-owned
Applied by consumer
The consumer decides when to apply it. Only then do its product tables change.
The record
If it moved, there's a reason on file.
Every promotion carries an approver, timestamp, checksum, and stated reason. An audit becomes a query, not an archaeology project.
Named approver
Every promotion is tied to an authenticated operator with step-up verification.
Ordered timeline
Acquisition, simulation, verification, and delivery all carry timestamps.
Checksummed package
Delivery batches are content-addressed, so what shipped is provable.
Stated reason
Approvals and overrides require a written reason kept with the record.
Put your external data on the record.
Operator access is provisioned while Confluendo expands from this first operated instance toward independently provisioned customer environments.