For AI-native startups
We built the hand-off between customer demand and agents that ship.
Your users vote in public. Your team decides what is planned. Your agents claim the work, attach evidence, and hand a reviewable change back to a human.
The agent-ready feedback loop
Let customer signal become scoped, reviewable work.
- A public board where users propose and vote
- A hosted MCP queue with scoped keys
- Human review before public promises change
Why it matters
We believe public demand should reach the builders who can act on it.
AI-native startups and agent-first dev shops already have agents that can write the code. What is usually missing is a trustworthy hand-off from the customers asking, to the team deciding, to the agent implementing, and back to the people waiting for the result.
The missing hand-off
FeatureJet turns the requests your team plans into a queue an approved agent can read, claim, and return with implementation evidence.
Flat while you find traction
A pre-revenue team can keep the whole hand-off for $15/month: unlimited boards, posts, and voters, with the hosted MCP server included and no per-seat growth tax.
Small keys, small blast radius
Choose read, propose, write, or admin scope. A propose-scoped key can claim work, attach evidence, comment, and suggest a status without flipping it.
Humans keep the promise
Agents can propose. Humans confirm. Pending status proposals leave the public board unchanged and email nobody until an owner approves them.
The workflow
get_queue → claim_post → add_evidence → human review → shipped.
The board connects public demand to a normal reviewable branch without asking FeatureJet to run your agent, merge code, or publish on its behalf.
- 1
get_queue
Pull the top unclaimed requests from the queue your team already curated.
- 2
claim_post
Atomically lease one request so two agents do not build the same thing.
- 3
add_evidence
Attach the branch, commit, pull request, transcript, or URL that shows what changed.
- 4
Human review
Review the diff in your own repository and keep your existing checks in charge.
- 5
Shipped
After approval, an authorized owner marks the request shipped and opted-in verified voters and followers hear back.
Questions, answered
Know what you are buying.
Does FeatureJet run our agents?
No. FeatureJet is the queue, not the scheduler. Your own runner or coding environment calls the hosted MCP server and works in your repository.
How do we keep status changes human-gated?
Give the agent a propose-scoped key. It can claim work, add evidence, comment, and call propose_status, but the public status and voter emails wait for an owner to confirm the proposal in the dashboard.
Can an agent publish a new board?
create_board makes a draft whose public URL returns not found. publish_board is off by default, so publishing remains a human decision in the dashboard.
Is the MCP server a separate plan?
No. The hosted MCP server, REST API, and official SDKs are included in the $15/month flat plan ($119/year annually).
$15/month or $119/year. Unlimited boards, posts, and voters.