CORE Admin & Developer Guide
Operate the Runink Platform
CORE is the shared platform under the Runink applications: the operators and the tenant API on a k0s cluster, the zero-trust security spine, the sovereign agent fleet, and the console that ties them together.
New to CORE?
Start here: Getting started: sign in, choose an instance, and read the Overview page.
What CORE is. CORE holds everything the Runink apps share and must not re-implement: the
Kubernetes operators and the ClientInstance tenant API, PKI and mTLS, envelope encryption,
the event mesh, inference serving, the edge, and the infrastructure as code. The apps (FACE, PULSE,
LUNA and FORGE) do not import CORE; code they share lives in shared libraries.
What you can do here:
- Overview: see whether anything is wrong, and where to go next.
- DevEx: run the platform with the
coreCLI, run CORE’s own coding agent, and follow the thirteenagents/binaries (seventeen entries on the console roster) through their workflows. - DataEx: see which models serve and which agents act, register connections and self-hosted data-access runners, and control who may do what.
- Intelligence: govern capital spend with the CapEx engine, map the data estate with Resolve, automate with playbooks, and ask grounded questions.
- FORGE: open FORGE’s chats in the Studio; CORE verifies every forged repository centrally.
For admins
- Sign-in, allowlists and the landing page
- Who may do what: the privileged-write allowlists
- Register a data connection
- Enrol a self-hosted data-access runner
- Understand the agent fleet
For developers
- Your first 30 minutes with the CLI
- The complete
corecommand reference - Run a coding session
- How a PR is reviewed and fixed
- Every console HTTP route
The five categories
The documentation follows the console rail, which is Overview · DevEx · DataEx · Intelligence · FORGE.
| Category | Audience | Question it answers |
|---|---|---|
| Overview | everyone | Is anything wrong, and where do I go next? |
| DevEx | the people who build and run the platform | What is deployed, how does traffic reach it, is the audit record intact, and what did the agents do? |
| DataEx | the people who consume what the platform decides | Which models serve, which agents act and within what limits, which sources CORE reads, and who may do what? |
| Intelligence | analysts and data owners | What does the platform know about the data estate, and did a commit ship? |
| FORGE | builders | What is being built on the platform? |
See the FAQ for cross-cutting questions.
CORE is proprietary software. © 2026 Runink. All rights reserved.