One controlled door to every business system
CKN Integration is the mediation layer that every industry Solution calls through. It keeps the service registry, workflows, routing, retries, compensation and external connectors in one place, so a business can change a process or connect a new system without rewriting each application, and every call leaves a trace you can audit.
A live map of every connection
Every route from each Solution through Integration to the business services. A failing line changes colour at once.
Know which call is failing
Failing operations, worst first, with their failure rate and error code.
Breakers stop a fault spreading
When a downstream service fails, the circuit breaker opens by itself and shows which processes are affected.
Design workflows on a canvas
Lay out the steps, gateways and approvals of a business process, then validate before publishing.
What CKN Integration does
Service and endpoint registry
Every connected system is registered with a clear contract, so you know who may call what and which service is healthy.
- Contract manifests and schema contracts per endpoint
- Transformations and retry policies defined as data
- Periodic health probes for every service
- Live system map with failure counts per route
Workflow and BPM as data
Business steps are data you can design, review and version, so a process change does not need a new code deployment.
- A fixed step vocabulary: INVOKE, gateways, wait on timer, event or callback
- Human review tasks where a person must approve
- Sub-processes, iteration over lists and scheduled runs
- Designer, test runner and version review queue in the console
Routing, retries and compensation
When a step fails the platform retries by policy and undoes completed work through compensation, instead of leaving data half done.
- Retry policy per endpoint and timers that persist across restarts
- COMPENSATE steps and a command to compensate a whole instance
- Exception queue and hold monitor for operators
- Permanent failures are not retried pointlessly
One entry API for every Solution
Every Solution calls through a single door and never needs to know the address or shape of each business service.
- Published entry operations with per-application client grants
- Request body validated against a schema first, target error codes passed through
- Idempotency-Key stops duplicate commands, replays kept for 30 days
- Command batch to submit many items in one call
External connectors and messaging
Reach outside systems through connectors that hold their own credentials, receive callbacks, and move events between services in order.
- Outbox poller reads business events per tenant, in order
- Webhook and callback intake that wakes a waiting workflow
- A Thai e-Tax document transmission connector, tested against a simulated provider
- Event subscriptions and a live WebSocket operation stream
Security and auditability
Every cross-service call carries a verifiable identity and scope, and operators can see what happened from the traces.
- Tokens verified against identity, tenant must match the token
- A delegation grant per call, never the caller's own credential
- Egress guard blocks connectors from internal and cloud metadata addresses
- Audit timeline, flow traces and exception queue in the console
Built and tested at this scale
These figures are counted from the code, the documentation and real test runs. They are not speed benchmarks.
Figures come from CKN's own test suites and benchmarks. Real results depend on each system's hardware and data volume.
What your business gets
Lower cost of connecting systems
A new Solution reaches the business services through entry operations that already exist, instead of rebuilding point-to-point links. A process change is made once, in the workflow.
Less risk of stuck data and duplicate orders
Retries, compensation and idempotency keys mean a failed or repeated call does not create duplicates or half-finished records. Work that needs a human decision goes to a review queue.
Control and traceability
Every call passes one point that checks identity, permission and tenant, so you get the whole picture in the console and an audit trail of who called what and when.
Calling a business operation through the entry API
Who relies on it
- Every industry Solution, through the entry API
- The 14 business services, called and polled for events through this layer
- Identity, which issues the tokens and delegation grants for every call
- The operator console, for flows, exceptions and service health
GET /entry/core-branch/search?limit=50 HTTP/1.1
Host: https://integration.example.com
Authorization: Bearer <access-token>
X-CKN-Operation-Code: CORE.BRANCH.SEARCH
HTTP/1.1 200 OK
{
"success": true,
"data": {
"processInstanceId": "<uuid>",
"status": "COMPLETED",
"result": { "...": "answer of the business service" },
"page": { "next_cursor": "<cursor>", "has_more": true, "limit": 50 },
"warnings": []
}
}