The comparison table against OpenRouter in the README is one of the smartest positioning moves I've seen in an OSS project recently — it immediately clarifies Manifest's value (local, free, transparent routing vs. cloud proxy with 5% fee). But there's room to amplify this further. Here are some specific suggestions:
1. Turn the OpenRouter comparison into a standalone landing page or blog post
The comparison table in the README is great, but it's buried below the fold. "Manifest vs OpenRouter" is a high-intent search query — someone searching that is actively evaluating options and is your ideal user. Consider:
- A dedicated page on manifest.build (e.g.,
/vs/openrouter) optimized for that query
- Expanding the comparison to include other routing solutions (Portkey, LiteLLM, Martian) to own the broader "LLM router comparison" search space
- Submitting the comparison to aggregator sites like AlternativeTo
This alone could drive significant organic traffic from developers already spending money on OpenRouter's 5% fee.
2. Publish cost savings benchmarks with real numbers
The "Cut Costs up to 70%" claim is compelling but unsubstantiated in the README. Adding a benchmark section with concrete numbers would dramatically increase trust:
- "We routed 10,000 requests through Manifest's scoring algorithm. X% were classified as 'simple' and routed to GPT-4o-mini instead of Claude Opus, saving $Y per 1M tokens."
- A cost comparison chart showing Manifest routing vs. always-use-best-model vs. OpenRouter
Developers making infrastructure decisions need numbers, not just claims. This would also give tech bloggers and YouTubers quotable data.
3. Create a "5-minute migration from OpenRouter" guide
Your Docker install is already one command — that's great. But explicitly showing the migration path from OpenRouter (change base URL, done) would reduce switching cost anxiety. Frame it as: "If you're already using OpenRouter, switch to Manifest in 5 minutes and save X%." Include before/after code snippets.
4. Add a "Who's using Manifest" or social proof section
At 4.4k stars and 243 releases, Manifest clearly has users. But the README has no social proof section. Consider:
- A logo wall of known users (even 3-4 would help)
- Testimonial quotes from Discord community members
- "X requests routed" or "Y tokens saved" aggregate stats from the cloud version
Social proof is the single highest-leverage README addition for converting visitors to users at your scale.
5. Expand GitHub Topics for discoverability
Current topics are solid but missing some high-search terms. Consider adding: model-routing, ai-cost-optimization, llm-proxy, ai-gateway, openai-proxy, self-hosted-ai. These map to actual search queries developers use when looking for solutions like Manifest.
Further reading: We've compiled patterns around competitive positioning, README conversion optimization, and B2B growth for developer tools in our open-source playbooks:
Manifest is solving a real pain point. These suggestions are about making sure more people find out about it.
The comparison table against OpenRouter in the README is one of the smartest positioning moves I've seen in an OSS project recently — it immediately clarifies Manifest's value (local, free, transparent routing vs. cloud proxy with 5% fee). But there's room to amplify this further. Here are some specific suggestions:
1. Turn the OpenRouter comparison into a standalone landing page or blog post
The comparison table in the README is great, but it's buried below the fold. "Manifest vs OpenRouter" is a high-intent search query — someone searching that is actively evaluating options and is your ideal user. Consider:
/vs/openrouter) optimized for that queryThis alone could drive significant organic traffic from developers already spending money on OpenRouter's 5% fee.
2. Publish cost savings benchmarks with real numbers
The "Cut Costs up to 70%" claim is compelling but unsubstantiated in the README. Adding a benchmark section with concrete numbers would dramatically increase trust:
Developers making infrastructure decisions need numbers, not just claims. This would also give tech bloggers and YouTubers quotable data.
3. Create a "5-minute migration from OpenRouter" guide
Your Docker install is already one command — that's great. But explicitly showing the migration path from OpenRouter (change base URL, done) would reduce switching cost anxiety. Frame it as: "If you're already using OpenRouter, switch to Manifest in 5 minutes and save X%." Include before/after code snippets.
4. Add a "Who's using Manifest" or social proof section
At 4.4k stars and 243 releases, Manifest clearly has users. But the README has no social proof section. Consider:
Social proof is the single highest-leverage README addition for converting visitors to users at your scale.
5. Expand GitHub Topics for discoverability
Current topics are solid but missing some high-search terms. Consider adding:
model-routing,ai-cost-optimization,llm-proxy,ai-gateway,openai-proxy,self-hosted-ai. These map to actual search queries developers use when looking for solutions like Manifest.Further reading: We've compiled patterns around competitive positioning, README conversion optimization, and B2B growth for developer tools in our open-source playbooks:
Manifest is solving a real pain point. These suggestions are about making sure more people find out about it.