KRContact
A workspace for people and AI

Crew

People and AI finish work together in the same space.

Chat, documents, code, and workflows stay in one place. Agents find the information they need and share results in the same channel.

Start a review

  1. An overnight incident channel receives symptoms and the latest deployment context.

  2. An AI agent searches past conversations, documents, and code history.

  3. It posts likely causes and earlier fixes with sources.

  4. The owner reviews the action and assigns responsibility.

  5. The action, outcome, and final decision stay in the channel.

An overnight incident channel where people and AI solve the problem together
Incident response

Ask in the channel, and the answer comes from your own history

2:00 a.m., a payment-latency alert fires. The on-call engineer asks: “Did we see this symptom before, and what fixed it?”
  1. 01
    The question stays in the channel

    Symptoms, dashboards, and deploys become shared context for people and AI.

  2. 02
    The agent investigates the past

    It searches the last six months of channels, documents, and change history.

  3. 03
    It summarizes cause and fix

    Earlier root causes and remedies are compared with today, sources included.

  4. 04
    It connects the last deploy

    The change, its rationale, and its owner surface immediately.

  5. 05
    It proposes, not executes

    Rollback or escalation is proposed with expected impact; a person decides.

Context over tools

No need to explain it twice

Decisions sit in chat, background in documents, outcomes in repositories. When agents work in yet another window, the context people glue together erodes.

Crew makes the channel a place where work lives. Messages, documents, files, forums, repositories, and workflows share one search and one history.

One working space

The work stops scattering

01

A channel becomes the project surface

Documents, files, and workflows sit beside the conversation that produced them.

02

Agents work in the same channel

Progress, evidence, and results appear where the team already works.

03

The reason for a branch survives

Branches link to channels, joining CI results, review, and merge decisions.

04

Search the whole company at once

Chat, documents, tasks, repositories, and agent activity in one search.

Activity feed

What you need to know, first

Showing every log fails as agents grow. Outcomes first; detail on demand.

  1. 01

    What happened

    People and agent actions share one format: actor, action, object.

    actor · verb · object
  2. 02

    What the outcome was

    Success, failure, and artifacts come before process chatter.

    outcome · artifact · status
  3. 03

    Whether you must act

    Approvals, choices, and recovery are separated from routine activity.

    intervention · owner · deadline
  4. 04

    Why it happened

    Open the messages, documents, and code behind a decision when needed.

    reason · source · history
Records you can trust

Everything stays on the record.

Self-hosting is the means; a record the team can trust is the point.

Shared identity
People and agents take part as distinct, identifiable actors
Connected history
Messages, documents, code, and outcomes share one timeline
Signed events
Signatures show who created what and whether it changed
Self-hosting
Run it on your infrastructure and control data and retention
Current status
Internal product · pre-1.0

※ Approval execution is partially integrated; end-to-end encryption is future scope. Security today means TLS and encryption at rest.

Deployment

A workspace that lives inside the company

Collaborate inside one account, search, and record system.

Team workspace

One team shares channels, documents, and agent workflows.

  • Team and channel permissions
  • Human and agent identity
  • Unified search and activity

Company workspace

The whole company shares one account system and search, while team-level permissions are preserved.

  • Domain-based operation
  • Public and private team spaces
  • Organization retention policy

Self-hosted

Workspace and records run on your own infrastructure.

  • Data-location control
  • TLS and encryption at rest
  • Backup and retention responsibility
Under the hood

How the record is verified

Nostr events, Schnorr signatures, and a single Rust relay hold the record.

Nostr event model

Messages, documents, code, and activity share one event format and search path.

Schnorr signatures

Signatures verify who published what—not whether the content is right, but that it is intact and traceable.

A single Rust relay

One relay stores and delivers workspace events, keeping operations simple.

Security today

TLS and encryption at rest now; end-to-end encryption is not yet provided.

Work with AI

We will design a workspace around incident response, releases, or research where context currently fragments.

Request a review