Quickstart
Deploy your first Hematite instance in under five minutes.
Prerequisites: A host running BizLinux with root access. Minimum 2 CPU cores, 4GB RAM, and 20GB disk space recommended for production use.
Step 1 — Install Hematite
Install the hematite package from your system's package manager:
# pkg install hematite
This installs all kernel crates, the API layer, WebSocket handler, and supporting tools.
Step 2 — Configure Your First Organization
Create an organization instance. Each org is a self-contained tenant with isolated content, templates, and access controls:
# hematite org create --name myorg \
--domain myorg.hematite.io \
--tier standard
This creates the org's configuration, generates default template overrides, and provisions the tenant namespace in Redis.
Step 3 — Start the Orchestrator
The noetic-kernel service manages agent pools, routes tasks, and maintains system health. Start it with systemd:
# systemctl enable --now noetic-kernel
# systemctl status noetic-kernel
You should see all kernel crates active: core, router, gates, handoffs, api, rdbms.
Step 4 — Access the Admin UI
The admin dashboard is available at your configured domain. Open a browser and navigate to:
https://myorg.hematite.io/admin
Log in with the default credentials (change them on first login):
Username: admin
Password: hematite
Step 5 — Create Your First Session
From the admin dashboard, create a new agent session. Select an agent type and configure your prompt:
# curl -X POST https://myorg.hematite.io/api/v1/sessions \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"agent_type": "general",
"prompt": "Explain the steel/pigment duality of Hematite.",
"domain": ["CRTV", "INFO"]
}'
The session will be created, routed through the adaptive scoring engine, and executed by an available agent. Results stream back via WebSocket or can be retrieved asynchronously.
What's Next
- Multi-Cognitive Orchestration Guide — Learn how to manage agent pools and routing
- API Reference — Full REST + WebSocket endpoint documentation
- Configuration — Environment-specific profiles, secrets, and tuning
- Explore Features →