Teams · Early access

One workspace.
Every access, accountable.

Share SSH hosts and Kubernetes clusters with your team—without sharing keys. Set access once, approve sensitive work, and know what every person or AI agent did.

$15 per user / month · No host or cluster limits · Cancel anytime

Protected

Good morning, Alex

Infrastructure overview

Resources

18

12 SSH · 6 Kubernetes

Active access

4

2 expire within an hour

Pending requests

3

Production approval

Team resources

Access follows identity, role, and environment.

prod-api-03

SSH

Approval required

payments-cluster

Kubernetes

Admin only

staging-web

SSH

Engineering

The old way doesn't scale

Stop distributing keys.
Start assigning access.

No credentials in chat

People connect to approved resources while secrets stay encrypted and out of sight.

One-click offboarding

Remove a member once and their workspace access disappears without rotating every server.

Identity on every action

Tie sessions and commands to a person or AI agent instead of a shared Linux account.

Shared inventory

One source of truth
for every connection.

Organize hosts and clusters by environment. Give teams the same clean inventory without copying configuration or credentials between laptops.

Unlimited SSH hosts and Kubernetes clusters
Shared groups, labels, and environments
Credentials encrypted and hidden
Production

12 resources · visible to Platform Engineering

api-primary

SSH · 10.0.12.4

Approval

payments

Kubernetes · us-east-1

Admin

worker-gpu-02

SSH · 10.0.18.9

Engineering

observability

Kubernetes · eu-west-1

Read only
Planned desktop integration

The Rumus desktop client is available today

Team control.
Local speed.

Rumus already gives engineers a native terminal, SSH client, and Kubernetes workflow. Teams will extend that existing client with shared resources and governed access—this integration is part of the proposed Teams product, not a feature available today.

Planned: workspace sync

Team hosts, clusters, roles, and revocations would sync into each member's signed-in desktop client.

Planned: access in context

Members could connect to approved resources or request time-limited access without leaving their local workflow.

Planned: centralized audit

Local sessions would remain fast and native while identity-linked activity flows back to the team audit trail.

Existing Rumus client:macOSWindowsLinux
Production access request

AR-1048 · created just now

Pending

Requested by

AK

Alex Kim

Platform engineer

Resource

prod-api-03

SSH · Production

Reason

Investigate API latency

Duration

60 minutes

Policy

ENG-PROD

Just-in-time access

Sensitive access
should expire.

Replace permanent production access with a clear request, a reason, an approver, and an automatic end time.

Human approvalTime limitedPolicy based

Human + AI audit

See the full session.
Not just the login.

Review requests, approvals, commands, policy decisions, and revocation as one identity-linked timeline—even when an AI agent is doing the work.

session · prod-api-03
LIVE · 00:14:32
09:41:02ssh deploy@prod-api-03ALLOWED
09:41:07journalctl -u api --since '10 min ago'ALLOWED
09:41:11▸ AI agent assumed task · identity verified214 MS
09:41:15kubectl get pods -n paymentsALLOWED
09:41:23rm -rf /var/lib/paymentsBLOCKED
09:41:24▸ policy violation · approval requiredENFORCED
10:41:02access expired · credential discardedREVOKED

How it works

One path in. Nothing unaccounted for.

01
Identify

Every person and agent connects with its own identity.

02
Authorize

Roles and policies decide which resource is available.

03
Approve

Sensitive sessions receive a reason, limit, and approver.

04
Audit

Requests, commands, and outcomes become one timeline.

Expected launch pricing

Rumus for Teams

A secure shared workspace for teams that manage real infrastructure together.

Unlimited hosts & clusters
Role-based access
Planned desktop integration
Approval workflows
Human & AI audit trail
Hidden shared credentials
$15/ user

per month, billed annually

No per-host or per-cluster fee

Questions

Before you join.

Is Rumus for Teams available now?+

Not yet. This page is validating demand before we commit to the full build. People on the list will be considered first for the private beta.

Are the UI examples on this page final?+

No. The interfaces shown on this page are early concepts used to communicate the product direction. The final features, workflows, and visual design may change based on validation and beta feedback.

Will teammates ever see shared credentials?+

The product direction is to let authorized teammates connect while keeping credentials encrypted and hidden from them.

How will Teams work with the Rumus desktop client?+

The Rumus client already exists on macOS, Windows, and Linux, but Teams integration does not exist yet. The proposed flow would bring shared resources, governed connections, access requests, and identity-linked audit events into that existing client.

Does it cover Kubernetes as well as SSH?+

Yes. The proposed workspace and policy model covers both SSH hosts and Kubernetes clusters.

Can we self-host it?+

Self-hosting is one of the options we are measuring. Select it in the follow-up survey after joining the list so we can prioritize it correctly.

Is $15/user/month final?+

It is the expected annual-plan price used to test willingness to pay. We may adjust packaging based on beta feedback.

Built for people and agents

Share access.
Keep control.

Join the early list and help shape secure infrastructure access for modern engineering teams.