Create account
Account is the commercial and governance boundary. Use one account per company, team, or controlled business unit.
account_id = acct_acme
Access Management
Register an account, request API keys, and control LLM context access.
MatrixArk treats account, tenant, user, session, and API key as first-class boundaries. Start with a cloud account or local deployment, then issue scoped keys for Codex/Cursor hooks, MCP servers, batch ingestion, and admin automation.
Sign in / Register
Continue with Gmail, or create an account with email and password.
Verified Gmail/Google and GitHub identities map to a MatrixArk user; email accounts store a salted PBKDF2 hash. Identity and API-key hashes persist in MatrixKV SQL or MySQL — never a raw token or password.
or use email
Registration
Simple for users, strict for production.
End users can subscribe to MatrixArk Cloud. Enterprise teams can run local or on-prem deployments for free/open-source TemporalStore and use MatrixArk Cloud services later. The identity model stays the same in both cases.
Create tenant
Tenant is the workspace boundary. Use tenants for prod, staging, departments, regulated data, or customer environments.
tenant_id = tenant_prod
Register users
User ids come from the app, hook, or SSO provider. MatrixArk maps them to stable hashes before context is stored.
user_id = alice
Issue keys
Issue different keys for hooks, MCP tools, batch ingestion, feedback, and admin automation. Keys can be user/session scoped.
scope = context:retrieve
Apply For API Key
Generate the exact request your admin or MatrixArk Cloud should approve.
Agent memory lessons
Registration is designed for agent context systems, not only ordinary API access.
Modern coding agents need organized memories, resources, and skills instead of flat chunks — and long-running applications need session batches, event/entity memory, operators, temporal compression, and time-aware recall. MatrixArk delivers this on an open, self-hostable stack: it keeps the caller surface simple while adding account, user, session, and API-key governance, backed by your own MatrixKV SQL or MySQL.
Agent hook keys
Issue scoped keys for Codex/Cursor hooks that send one message at a time, retrieve ContextPacks before the LLM call, and ingest assistant/tool output after the call.
Session batch keys
Issue batch-ingestion keys for session windows, rolling commits, idle-time commits, and one-pass extraction across 20-message logical batches.
Resource and skill keys
Issue resource-ingestion keys for files, runbooks, skills, and operational knowledge, then let MatrixArk attach L0/L1 summaries and TemporalStore indexes.
Governance keys
Issue admin keys separately for account status, user lifecycle, key rotation, SSO mapping, audit replay, and emergency tenant disablement.
Access Management
What admins control after registration.
Account and tenant status
Disable one tenant for an isolation incident or disable the whole account for a customer suspension without deleting historical context.
User lifecycle
Register, list, enable, or disable users. Disabled users are blocked for API-key-authenticated context calls.
API key lifecycle
Create, list redacted metadata, rotate, revoke, and expire keys. Raw keys and hashes are never returned by inventory APIs.
Audit and usage
Every context and admin operation records account, tenant, role, key id, user id, session id, and timestamp for replayable governance.
MatrixArk Cloud
Ready to register?
Send your preferred account id, tenant id, integration type, and expected context volume. We will issue scoped keys for the right deployment mode.
Apply now
Cloud subscription for end users and teams. Local/open-source TemporalStore setup for developers and on-prem enterprise pilots. API-key roles map cleanly to each flow: hook, retrieval, resource ingestion, session batch extraction, feedback, replay, and admin governance.
founders@matrixark.ai