Open beta now. Paid tiers when the product earns them.
We are onboarding a small group of technical startups with 3-30 engineers that want approved specs before more execution noise.
For teams willing to shape the review flow with us before Freshbase becomes generally available.
- checkUnlimited Bases and team members during beta
- checkInbox review for decisions, specs, ADRs, and criteria
- checkLinear, GitHub, Notion, Slack, and MCP included
- checkDirect Slack channel with the founders
- check50% off the first paid year, locked in
- checkNo credit card
We'll reply within 48 hours with a calendar link.
For organizations that need Freshbase deployed around stricter security, procurement, and data-boundary requirements.
- addEverything in Founding Teams, plus:
- checkSSO (SAML/OIDC) & SCIM provisioning
- checkDPA, MSA, and audit support
- checkDedicated tenant and BYO LLM option
- checkData retention policies and audit logs
- checkQuarterly business review with the founders
Enterprise access opens after the beta cohort.
Compare access
| Founding Teams | Enterprise | |
|---|---|---|
fact_checkReview Flow | ||
| Inbox review for proposed decisions | check | check |
| Specs, ADRs, and acceptance criteria | check | check |
| Private drafts before promotion | check | check |
descriptionOutputs | ||
| Approved specs | check | check |
| User journeys | check | check |
| Architecture decision records | check | check |
| Linear handoffs with rationale | check | check |
| Custom approval templates | — | check |
syncIntegrations | ||
| Linear sync | check | check |
| GitHub, Notion, and Slack | check | check |
| MCP Server (Cursor, Codex, Claude Code) | check | check |
| Dedicated API access | — | check |
| Custom integrations | — | check |
auto_awesomeAI Boundary | ||
| AI proposes, humans approve | check | check |
| Source-linked rationale | check | check |
| BYO LLM option | — | check |
shieldSecurity & Compliance | ||
| Encryption at rest & in transit | check | check |
| SSO (SAML/OIDC) | — | check |
| SCIM provisioning | — | check |
| Audit logs | — | check |
| Custom data retention | — | check |
| SOC 2 Type II | In progress | In progress |
support_agentSupport | ||
| Direct Slack with founders | check | check |
| Beta feedback loop | check | check |
| SLA guarantee | — | check |
| Dedicated onboarding | — | check |
Frequently asked questions.
Can't find what you're looking for? Check our docs or reach out to us.
No. Meetings are an intake surface. freshbase turns conversations into proposed decisions, specs, ADRs, and acceptance criteria, then routes them through Inbox before they become shared team context.
Only approved Inbox items. Private drafts, rough thoughts, and raw meeting material stay separate until a human promotes them into the collective base.
Approved specs, product decisions, ADRs, acceptance criteria, user journeys, and Linear handoffs. Each artifact keeps provenance back to the conversation and the approving decision.
Linear remains the execution surface. freshbase sends approved context, rationale, criteria, and links downstream so tickets carry the why instead of replacing your delivery process.
MCP gives tools like Cursor, Codex, and Claude Code access to approved product context, not private brainstorming or raw transcript sprawl.
Founding teams get free access, direct founder support, and a tight feedback loop while we tune the approval flow, integrations, and product boundaries.
The product is designed around private drafts, explicit approval, and enterprise controls. Team intent should stay yours, and model processing is scoped to generating outputs inside the service.
Yes. Keep your meetings, planning calls, docs, and Linear workflow. freshbase adds the review gate between conversation and shared truth.
Keep the why alive
from conversation to commit.
Freshbase turns product and engineering conversations into approved context your team can review, trust, and route into the tools where work actually ships.
Early teams help define the approval layer before general availability.