Can we start open source and upgrade later?
Yes. The workflow stays consistent across plans, so teams can start self-hosted and move into Team, Hosted, or Enterprise when they want less operational overhead.
Pricing
Pricing that fits the way your newsroom actually works
Start with the open-source stack, move into a shared editorial workspace, or hand off the infrastructure entirely. Every tier keeps the project-scoped workflow intact so you do not have to relearn the product as you grow.
Open source foundation
Project-scoped ranking and review
Upgrade without changing your workflow
Pick the operating model that fits your stack
Start open source, move to a hosted workflow later, or keep the whole pipeline in your own infrastructure from day one.
Team
$149/mo
A shared editorial workspace for small newsletter teams shipping every week.
- 3 editor seats
- Review queue tooling
- Reference corpus training
- Priority updates
Hosted
Popular$399/mo
Managed infrastructure for editors who want the workflow without running the ops layer.
- Managed upgrades
- Inbound newsletter parsing
- Team collaboration
- Email support
Enterprise
$1499/mo
Private deployment, custom plugins, and security review for larger media or research orgs.
- VPC or on-prem
- Custom source plugins
- SLA-backed support
- Migration help
Open Source
$0/mo
For teams that want full control and are happy to run the stack themselves.
- Unlimited projects
- Docker Compose setup
- Bring your own models
- Community support
Compare plans at a glance
Use this matrix as a starting point for evaluation. We can tune packaging and limits later, but these examples show how the plans differ in practice.
Feature | Open Source | Team | Hosted | Enterprise |
|---|---|---|---|---|
Deployment | Self-hosted | Shared cloud | Managed hosting | Private cloud or on-prem |
Editor seats | Unlimited | Up to 3 | Up to 10 | Custom |
Review queue | Included | Included | Included | Included |
Inbound newsletter parsing | Manual setup | Guided setup | Included | Included |
Model configuration | Bring your own | Shared presets | Managed defaults | Custom model policy |
Support | Community | Priority email | Managed support | SLA + onboarding |
Pricing FAQ
These are the questions most teams ask before choosing a plan. We can refine the details once you decide how hands-on you want to be.
Do all plans support project-specific ranking?
Yes. Project-scoped relevance, review queues, and source configuration are part of the core product rather than premium-only add-ons.
Can we use our own models and data sources?
Yes. The open-source and enterprise paths are especially flexible, but every tier is designed to work with the sources and model setup that match your editorial process.
Turn scattered feeds into a shortlist you can trust.
Connect the sources you already trust, train one project on your editorial taste, and let the next issue start with ranked content, summaries, and a draft outline instead of a pile of tabs.
- Project-scoped ranking
- Editorial memory
- Draft-ready research
01
Rank the signal
Pull your sources into one project and get a shortlist shaped by what your editorial team actually trusts.
02
Keep the context
Entity summaries, source history, and authority cues stay attached so every candidate story arrives with useful framing.
03
Start from a draft
Move from ranked research to a draft outline without rebuilding the same judgment call from scratch every week.