AI-first project workspace

Everything your projects run on, in one workspace.

Repositories, domains, servers, tech stack, deployments and documents — with credentials and .env vars stored right where they belong. Organized per project, shared with your team, access-controlled.

One home per projectRole-based accessSecrets masked by defaultFull activity log
acme-webWeb app
StackNext.jsPostgresVercel
Repositorygithub.com/acme/web
Domainacme.com Live
Serverprod-1 · sgp1
Credentials & env8 secrets
STRIPE_SECRET_KEY
DATABASE_URLpostgres://…5432/acme Revealed
DATABASE_URLrevealed by you · just now · logged

Built for the teams who hold the keys

FoundersIndie hackersSmall software teamsAgenciesFreelancers
Why it exists

The scattered way of working, replaced

Most small teams keep their operational knowledge in a dozen places. Kyron pulls it into one.

Repo in one place, domain in another, deploy notes in someone’s head.

Now

One project page with its stack, repos, domains, servers and docs together.

Secrets and env vars scattered across .env files, spreadsheets and DMs.

Now

Credentials stored with their project — masked by default, audited on reveal.

No clear picture of who on the team can touch what.

Now

Role-based access per project and a full activity log across the workspace.

Everything in one place

Built around your projects

Six connected modules, all hanging off the project they belong to — so the repo, the domain, the server and the secret are one click apart, not one search away.

Projects hub

Every project gets one page — its tech stack, repositories, domains, servers, docs and secrets. Open a project and see everything it runs on.

Repositories

Connect the git repositories behind each project, so the code — and exactly where it lives — is never a guess or a Slack search.

Servers & domains

Keep hosts, IPs and domains beside the projects that run on them. No more hunting through email for that one DNS record.

Deployments

Track what is live where, per environment — type-aware for web, mobile and services, so the record fits the project.

Documents

Runbooks, onboarding notes and architecture decisions in markdown, versioned alongside the work instead of lost in a drive.

Credentials & env

API keys, passwords, tokens and environment variables — stored with the project they belong to, masked by default and reveal-audited.

How it works

Set up in three steps

From empty workspace to your whole team working from one source of truth.

01

Create your workspace

Spin up a workspace for your company in seconds. No credit card, no setup call.

02

Add your projects

Bring in each project with its repos, domains, servers, stack, docs and secrets.

03

Invite your team

Add teammates with scoped roles so everyone gets exactly the access they need.

Team & roles

Your team, with exactly the right access

A workspace is only useful if the whole team lives in it. Invite everyone, then let roles decide who can see, edit or reveal each project and its secrets — so access maps to responsibility, and nothing leaks by accident.

Scoped roles

Owner, admin, member or a role you define. Each role is a clear boundary, not a vague setting.

Per-resource access

Decide who can view, edit or reveal each project, credential and document — down to the resource.

Invite in seconds

Add teammates by email and they are productive in minutes. Contractors get scoped access that expires when the work does.

Attributed activity

Every change is tied to a person, so the workspace can always tell you who did what, and when.

Members4 people
K

You(you)

Full access

Owner
AR

Aditi R.

Manage projects

Admin
MK

Marcus K.

View & deploy

Member
JD

Jamie D.

Docs only

Contractor
Contractor can see documents, but never reveal a secret.
Security by default

Secrets stay the most protected part

Credentials and env vars live alongside the rest of a project, but they’re held to a higher bar — masked, audited and access-controlled, so keeping everything together never means keeping it exposed.

Masked by default

Secrets live in the same workspace as everything else — and they are its most protected part. Hidden until someone deliberately reveals them.

Reveal audit trail

Every time a value is unmasked it is recorded — who, what and when — so exposure is never silent.

Role-based access

Granular roles decide who can view, edit or reveal. Access maps to responsibility.

Full activity log

A running history of changes across projects, credentials and team, so nothing happens off the record.

Pricing

Start free. No card required.

Get organized today. Deeper access controls and history arrive with Team.

Free

$0

For founders and small teams getting organized.

  • One workspace
  • Projects, repos, domains & documents
  • Credentials masked with reveal audit
  • Up to a small team
Start free

Team

Next up

Coming soon

For growing teams that need deeper access control.

  • Everything in Free
  • Advanced roles & permissions
  • Extended activity history
  • Priority support
Start free today
FAQ

Questions, answered

Everything it runs on: its tech stack, git repositories, servers, domains, deployments and markdown documents — plus its credentials and environment variables. Open one project and you have the full picture in one place.

Get started

Bring your projects together.

Create your workspace in seconds and give your team one place for every repo, domain, document and secret. Free to start, no card required.