Your team's AI setup, in any tool.
MCPs, skills and context versioned in one place, written in the format Claude Code, Cursor and Codex expect. New people on the project run dot init && dot pull and work to the team's standard from minute one.
$ dot init
linked to acme/api · team setup v1.4.0
$ dot pull
3 targets · backup saved · 0 conflicts
$
In the setup
- contextCLAUDE.md, team rules and conventions
- MCPsthe same MCP servers for everyone
- skillsworkflows the team reuses in every project
- versionsemver, diff and rollback on every change
- vaultsecrets referenced by name, kept only on your machine
Right now, that setup lives on each dev's machine.
A CLAUDE.md copied from project to project.
Everything configured again when you switch tools.
The same AI answering differently for you and your teammate.
One setup. Each tool's native format.
Adapters translate the same setup into the files each tool already reads. Moving from Cursor to Claude Code? dot switch claude.
Project setupv1.4.0
- Context
- CLAUDE.md
- MCPs
- postgres-mcp, github-mcp, context7
- Skills
- code-review, migration-writer
- Preferences
- model, language, style guide
- Claude CodeCLAUDE.md.mcp.json.claude/skills/
- Cursor.cursor/mcp.json.cursor/rules/
- CodexAGENTS.mdconfig.tomlskills/
- GenericDOT.mddot.mcp.jsondot/skills/
Example setup. Antigravity adapter is being mapped.
Every change becomes a version.
History with diffs, rollback in one command, and a view of who on the team has fallen behind.
- v1.2.0
- v1.3.0
- carla·driftv1.3.2
- ana·up to datebruno·up to datev1.4.0
dot statusweb squad
Demo data.
dot rollback 1.3.2- mcps: context7
- skills: migration-writer
- skills: legacy-lint
- context: CLAUDE.md, 2 lines
Secrets never leave your machine.
MCP API keys and tokens stay in the CLI's local vault and enter the setup by name only. Before overwriting any file, dot takes a backup. That holds on every plan, Free included.
What people usually ask
I already version my configs with dotfiles in Git.
Dotfiles store raw files. They don't compile for multiple tools, have no secrets vault, and can't show who is out of date.
My team only uses one tool.
Standards, onboarding and history pay off with a single tool. And the next dev who shows up with a different one gets the same setup.
My devs won't adopt yet another tool.
dot doesn't replace the IDE or the agent. It writes the files they already read. Devs keep their tool and get the team's setup.
What happens when a tool changes its format?
Each tool has a versioned adapter. The format changes in the adapter; the team's setup stays the same.
Free for one dev. Per seat for the team.
Expected launch pricing. Secrets vault and backups are included in every plan.
Individual
Free
dot start
$0
1 project, 1 tool. Free forever.
Pro
dot flow
$12/mo
Unlimited projects and tools.
Power
dot pilot
$29/mo
Per-client workspaces and Registry publishing.
Team and company
Team
dot squad
$19/seat
Squads of 3 to 15 devs, private registry, drift dashboard.
Business
dot scale
$39/seat
SSO, exportable audit log and MCP policies.
Enterprise
dot govern
Contact us
Custom contract, SLA and dedicated deployment.
Dolfi is asleep.
Join the waitlist. When the first version of dolfinsis dot is ready, Dolfi will wake up and let you know by email.