Ryker / Docs / Access and data
Access and data
You choose the host, model account, repositories, and systems Ryker can use. Its own records stay in your database; hosted models receive the context needed to do the work.
On this page
Where data goes
Ryker stores requests, work history, memory, pending replies, and encrypted integration credentials in PostgreSQL on your host. The keys are generated during installation. A usable backup needs both the database and those keys.
A hosted model can receive messages, repository content, retrieved memory, and tool results relevant to a request. Choose a provider and account whose data terms fit your team. The included voice transcription and search-by-meaning models run locally.
Connected services receive the requests made to them. Slack carries conversations, GitHub carries code and review activity, and Emisar executes and records infrastructure actions. The console serves its own fonts and scripts and includes no third-party analytics.
Who can request and manage work
| Interface | Access |
|---|---|
| Slack | Active full members can ask questions and confirm code tasks. Configured operators manage settings, incidents, saved automation, publication, and task controls. Guests, Slack Connect users, bots, and deactivated accounts cannot authorize work. |
| GitHub | A person needs write or admin repository access to request work through GitHub. |
| Console | Everyone signed in can see and change the whole installation. Invite only people who should have that access. |
| Emisar | Its policy determines who can approve an infrastructure action. Slack operator status does not grant that permission. |
App alerts use their configured channel behavior. Webhook sources have their own authentication and fixed destination; incoming payloads cannot select a different environment. See webhook setup.
Limit what a task can reach
An environment selects repositories and an optional Emisar account. A code task changes one permitted repository, with other repositories available as read-only context. Draft publication is separately enabled, and people control merging and releasing code.
co:op runs model sessions in containers with separate working copies. The bundled worker has a private Docker daemon; model containers do not use your host’s Docker socket.
The GitHub App’s private key, Slack credentials, Emisar credentials, and webhook credentials stay with Ryker. The trusted worker receives short-lived tokens scoped to one repository for fetching code or authorized publication. Publication credentials stay outside the model’s sandbox.
For infrastructure, Emisar checks the account’s runner access and action policy. Allowed actions run, approval-required actions wait, and denied actions cannot run. Messages, memory, and instructions cannot expand these permissions.
The installation host remains trusted. Protect access to the host, database, keys, and backups as you would the connected systems. Keep the console bound to loopback or use the documented remote-access setup.
Control remembered information
Background learning is enabled by default and can learn from retained conversations in observe-only channels. Pause it under Memory › Learning. Inspect or remove facts, topics, and guidance in the console.
Recall checks access to the source context, including current Slack membership. Private-channel knowledge is not available to every conversation. See recall rules and memory expiry before choosing retention settings.
Inspect and retain records
A request’s timeline records its context, tool activity, checks, and reply. A proposed action, approval, and observed result are separate records.
Choose history limits under Settings › Data retention. Shortening a limit can delete older data. Backups contain credentials and decryption keys; keep a protected copy away from the host. The operations guide covers backup, restore, and retention.
Report a vulnerability
Follow the repository’s security policy. Keep credentials, private messages, and customer data out of public issues.
Source and license
Ryker’s source is on GitHub under Business Source License 1.1. The current license allows non-production use. For production licensing, contact licensing@emisar.dev.