14 days free for teams of up to 5. No card needed.
How it works
01
Connect machines with one command
Run it on a Mac mini, a VPS or the office server. The machine joins the pool in seconds, and VECTA detects its system, memory and agents.
$curl -fsSL https://vecta.build/install.sh | sh -s -- <CODE>
Linux today. On a Mac, install the VECTA app.
02
Create a project in the browser
Pick a GitHub repository. VECTA suggests a setup script and machine requirements from its files; add secrets and save.
03
Give a task — VECTA picks the machine
Anyone on the team starts a task from the web or a phone. It goes to a free machine that fits the project, or waits its turn in the queue.
One pool. One conversation. Projects in the browser.
Shared pool
No task waits for “its” machine.
Every machine the team connects is in one pool, and a task takes the next free one that fits. Each machine shows how many tasks it is running.
Shared conversation
The whole team in one conversation with the agent.
Anyone can steer, approve or take over. Everyone sees who asked for what, who is typing and who leads the task; questions from every agent wait in one list.
Projects from the web
No SSH, no per-machine setup.
The setup script, secrets and machine requirements live with the project, not on a server somebody configured by hand.
Your machines, or ours.
Mac minis, VPS and the office server sit in one pool with VECTA Computers. You pay per person, not per machine, so connect as many as you have.
Your machines
Any Mac, Linux box or VPS your team already has. Agents work with the sign-in done on that machine, and each machine shows which agents are signed in.
Whose Claude or Codex plan runs on a team’s machines?
Whichever account is signed in to the agent on that machine. Personal plans are usually meant for one person, so check your provider’s terms; a team plan or API keys may fit better.
How are project secrets stored?
Encrypted on our server, and never shown again once saved. A task gets them only while it runs, for its setup script and its agent. The agent can read them, so use test keys, not production ones.
What if a machine goes offline during a task?
When the project has a Git remote, VECTA saves the work to the task’s own branch after every agent reply. Wait for the machine, or continue the task on another one from there.
How do we pay for Team?
For now, with VECTA credits from any Owner’s own balance: 20 credits per person for 30 days, charged up front. One credit is $1. Credits come from Founding Builders or from us; card payment isn’t open yet.
What happens when the trial ends?
Your people, machines, projects and history stay. Until Team is paid, new tasks run on one machine and nobody new can join. The trial lasts 14 days, once per workspace, for teams of up to 5.
Put every machine to work.
Connect the machines you already have, create one project and give the team its first task.