Developer tools decision
Primer3 API
A single developer can build and host a useful Primer3 HTTP wrapper (API, auth, parsing, deployment) in about a week; the paid product's dashboards, analytics, and managed scaling are the main things you'd trade off.
Visit website↗Built by Iván Córdoba, who ships 4 products in this index
$4/mo
$48/yr
Read off the official pricing page.
$50one-off30 h to build
$0/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 2 seats.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Accept primer design parameters over HTTP, run primer-design engine, parse results, enforce per-key rate limits, return JSON results.
What it still won’t have
- Hosted dashboard with usage statistics and detailed analysis
- Built-in priority support and managed API key lifecycle
- Guaranteed scalability and performance SLAs
- Billing, subscription management, and upgrade paths
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal Primer3-compatible REST API in Python (Flask or FastAPI) deployed as a single Docker container on a small VPS or serverless platform. Scope: POST /v1/primers accepts JSON primer-design parameters, validates inputs, invokes a local Primer3 CLI binary (assume installer step), parses Primer3 output into JSON with primer sequences and basic metrics, enforces API-key header authentication and per-key rate limits (50/month default), and returns structured responses and error codes. Out of scope: multi-tenant billing dashboard, analytics UI, enterprise SSO. Require: input validation, clear error handling, unit tests for parsing/validation, and Dockerfile + simple deployment script.
How we checked
How the score was reached
- Build verdict base78
- 3 cited sources+3
- Price verified on pricing page+3
- Evidence score84
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productPrimer3 API homepage
- official pricingPrimer3 API pricing section
- official productPrimer3 API features
Integrity checks
What held up, and what did not.
