Platform · People

KERNSTACK Collaboration

Collaboration is the project’s built-in conversation layer: topics on a board (Backlog, Active, Review, Done), messages with attachments, channels that bind a Telegram group or a WhatsApp conversation to a topic, and @agent — mention it for answers and summaries, or, in code mode, for a working demo built on a sandbox branch and returned as a link in the same thread.

Collaboration Board
Talk to us Read Collaboration Docs → Software Lifecycle Cloud →

Why teams replace assembled cloud services with KERNSTACK Collaboration

Teams otherwise discuss work in a chat tool that never sees the diff, with decisions evaporating into scrollback. On KERNSTACK the conversation belongs to the project it discusses: the board, the agent, and the deploy history share one home.

Topics, not scrollback

A conversation is one topic per piece of work, moving across the board’s states, shareable as a view-only board link with partners who cannot log in. Attachments land in the project. When a topic needs a decision, the record of who decided and what shipped stays attached to the topic — the audit trail of the soft side of engineering, kept with the same seriousness as the deploy’s.

Channels meet partners where they are

Bind a Telegram group (Settings → Channels) and invite partners by link; bind a WhatsApp conversation to a topic and messages flow both ways, media included, with agent and system replies delivered back into the chat. The client who will never open a console answers in four minutes on WhatsApp, on a topic the team sees on the board — one conversation, several front doors.

  • @agent answers and summarises in-thread; code mode returns live demo links from agent environments
  • Plan mode on a topic asks @agent for an OpenSpec plan — proposal, requirements, scenarios, and tasks — and keeps product edits closed until the card is approved
  • Channel bindings are per project (Telegram) and per topic (WhatsApp) — clients never see each other
  • Board links are view-only for partners; no console accounts needed for oversight

SDKs & Language Integration

Every KERNSTACK environment vendors typed SDK packages into .kernstack/ so both engineers and coding agents in Agent Sandboxes can call Collaboration without external credentials:

  • Go SDK: kernstack CLI and console (no SDK client)
  • Node.js SDK: kernstack-sdk
  • Python SDK: kernstack_sdk
  • PHP SDK: kernstack/sdk (Composer)
FAQ

Frequently asked questions

No. A view-only board link covers oversight, and Telegram or WhatsApp bindings put the conversation in tools partners already use. Accounts are for the people who deploy.

Answer project questions, summarise board and thread state, and — with Agents enabled and hosted git available — build demo changes on agent branches and reply with the live environment link. Plan mode asks for an OpenSpec plan first: a card in the thread, with product edits and deploys closed until someone approves it. Production remains a human-approved promotion away.

For project work, it is designed to be where the work is discussed; for company-wide chat, keep your tool. The boundary is deliberate: conversations here are attached to projects, topics, and deploys, which is what chat cannot give you.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Category PillarThe Software Lifecycle CloudHow infrastructure, code, intelligence, and collaboration unify in one project graph.Use Case · AgenciesAgency client deliveryAgency client delivery on KERNSTACK: every client a declared project, preview links clients approve, handoff is the project itself.Use Case · AgentsAgent operations consoleAn agent operations console on KERNSTACK: every agent branch, demo environment, plan, and approval state visible in one project view.Use Case · OperationsApproval workflowApproval workflows on KERNSTACK: invoices, contracts, and exceptions pause at titled human steps inside a declared workflow — decided in context.Use Case · ProductCustomer portalA customer portal on KERNSTACK: clients see account status, shared files, and conversation in one project — no more emailed screenshots.Use Case · OperationsHuman review queueA human review queue on KERNSTACK: workflows park uncertain items at titled steps, reviewers work one queue, every verdict recorded.Use Case · ProductNotification fanoutNotification fanout on KERNSTACK: one domain event, mail and chat steps declared in a workflow, delivery receipts stored as rows.Platform · AgentsAgent sandboxesIsolated sandboxes for coding agents

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →