Launch destination intelligence
Directories die quietly. We check, every day, and publish what we find.
Opterva tracks 10 launch destinations and has recorded 130 checks against them. Where we do not know something, we say so instead of estimating it.
Free while we build. No card, no plan chosen yet.
Live from the registry
just now
10
destinations
130
checks recorded
0
confirmed usable
Currently failing
Slant
Server error 526 — 13 checks in a row. This is the kind of thing a list nobody verifies would still be recommending.
Figures read from the registry when this page was built. Nothing here is an estimate.
Where this is
Opterva is early. Here is exactly what it does and does not do.
The category is full of confident lists nobody verifies. We would rather show you a short honest one than a long invented one, so this page tells you what is missing as plainly as what is not.
Works today
- A registry of 10 real destinations, checked automatically every day
- The result of every check kept, so a failure that lasts is distinguishable from a bad minute
- Products, campaigns and the content you write for each destination
- An append-only activity trail you can export, covering every change
- Metrics we have not measured shown as not known, never as zero
Not built yet
- Recommendations. Nothing yet tells you which destinations suit your product — that is the next thing being built
- Generated copy. Nothing drafts your submissions
- Submissions. Atlas does not submit anything on your behalf
- Billing. Nothing charges anyone, and no price has been set
To be precise about the registry: a daily check tells us a site answered, not that it still accepts submissions. Confirming that is human work, and none of the 10 has been confirmed that way yet. So every one of them is listed as not known.
The last check
What 10 destinations actually did when we asked.
- 4
- refused our checker
- 4
- answered
- 1
- asked not to be checked
- 1
- returning an error
4 of these refused our checker outright, and that counts against nobody. Blocking bots is normal and sensible, and several of the best destinations here do it. We record that we were refused and leave the verdict to a person.
How it works
Three steps that exist and one that does not, yet.
01
Add your product
Name it and give it a URL. We store what you type — nothing is inferred from your page, because nothing reads it yet.
02
Browse the registry
Every destination we track, with what the last check found and when. Anything unmeasured is marked not known.
03
Plan a campaign
Pick destinations, write what each one needs, and track where each submission has got to. You submit; we keep the record.
04
Recommendations
Not built. When it exists it will say which destinations suit your product and why — and until then nothing here pretends to know.
Start with what is verified.
A short list we actually check beats a long one nobody does. Create a workspace and see the registry as it really is.
Create a workspace10 destinations · last checked just now