You set the goal
Name the outcome and the role that should own it. Starboard is where that decision lives, not inside a single chat that disappears.
Direct the agents. Keep the record.
Starboard is the agent manager. You set the goals, organize a team of specialized agents, delegate the work, and follow the progress. Rutter is the execution harness underneath. It runs each worker with that worker’s permissions and skills, and it carries the project’s context, memory, and evidence from one piece of work to the next.
How it works
Management and execution stay separate. You do not have to be the one holding every detail, and a worker does not get a free hand.
Name the outcome and the role that should own it. Starboard is where that decision lives, not inside a single chat that disappears.
The goal goes to one specialized worker. The first roles are a developer, a forward-deployed engineer, and a site reliability engineer. Finance, accounting, and marketing are the same kind of role, added as those skills are ready.
The harness runs that worker’s duty and only that duty. A person building a change is not the same role as the person responsible for keeping it up. Decisions, open work, and evidence stay in the project for the next session.
You can see what is in progress. Work that spends money, changes production, or erases history waits for you.
Two products, one stack
The place you direct the team. You organize the work, choose the role, delegate the goal, and watch progress. Starboard is how a person stays in charge of agents instead of chatting with them one at a time.
The runtime under the manager. It runs specialized workers with scoped permissions and skills, and it keeps durable project context, memory, and evidence with the work. A new session continues from that record.
Where it helps
These are the roles you can direct now. The manager is built so later roles can cover other work, including finance, accounting, and marketing.
You give a building goal to the developer role. Rutter keeps the decisions and the evidence of what is actually done, so the next session does not reconstruct the project from scratch.
A rollout or a customer delivery has its own duty. That role is separate from the person writing the change, so delivery work does not borrow implementation permissions.
The site reliability role holds the reliability duty. It does not also hold the duty of making the change. You can see the handoff instead of mixing both jobs in one agent.
Yours to direct
You bring the model. Starboard does not sell compute. Rutter’s job is the part a chat window forgets: who was allowed to do the work, what was decided, what is still open, and what evidence is required before something is called done.
Founder license
The price is USD $100 per year and excludes tax. Applicable tax is added at checkout. The subscription renews automatically until you cancel. The trial starts when the subscription starts and ends 30 days later. The full $100 plus tax is charged then if you do not cancel. It is not a smaller prorated charge. The first license year ends on the anniversary of the trial start, so the trial counts inside that year and about 11 months of paid access follow the trial. Later charges fall on that anniversary, not a year after the first charge.
Trial
A payment method is collected when you start. The $100 charge comes after the trial, not on the first day.
Then
Plus applicable tax. This is one founder license, not a seat pack and not a price that is locked for life.
Renewal
Cancel in the billing portal before the trial ends if you do not want the first $100 charge. After that, cancel before the next year.
Checkout is not open yet.