Clone a repo. Run one command. Start coding.
DevSet reads your project, figures out what it needs, and sets it all up: Node packages, Python virtual environments, .env files, and one command to start every service. No AI, no network calls during analysis.
The problem it solves
Every new repo costs 30 to 60 minutes of guessing. Tick what you have done by hand before, and watch the time add up.
How it works
DevSet runs seven stages in a fixed order. Click a stage to see what it does.
Try it: run DevSet on a pretend project
Pick a project and set what already exists on your machine. Then press Run and see the plan DevSet builds.
Tip: tick all three "already exists" boxes to see the "already configured" result.
Press "Run devset" to start.
How DevSet detects your tech
Every clue adds points. Enough points and a technology is confirmed; a few points and it is only possible. Tick the files your project has.
Bars show the score. Marks show the "possible" and "confirmed" lines for each technology.
Lockfiles decide the install command
DevSet uses your lockfile so everyone installs the exact same versions. Two lockfiles in one folder is a conflict, and DevSet warns you.