Curated research corpus
Papers from seven sources, organized around the terminology the field actually uses rather than whatever a generic feed happened to catch.
Research portal
Every rare disease deserves a research home.
The literature exists. The access layer usually does not. Most communities are left with scattered PDFs, institutional memory, and search terms that collapse the moment the wording drifts.
This packages the same retrieval and curation system behind RevasserKernel into one durable surface for a single condition: papers, semantic search, collections, exports, and a portal your community can keep using after launch.
Why this exists
The research was real. The container around it kept failing.
Patients and advocates do not need another search box. They need one place where the field’s language, literature, and working knowledge can hold together long enough to compound.
RevasserKernel was built because rare-disease research usually lives in fragments: one good review article, three key papers nobody can find twice, and an exhausted volunteer who knows where the bodies are buried.
The portal fixes that failure mode. It gives a condition a named home, a curated corpus, and a retrieval layer strong enough to survive terminology drift, volunteer turnover, and the ordinary entropy of patient-led infrastructure.
That is the actual offer: not a prettier website, but a durable operating surface for the research itself.
What arrives
One condition. One durable research surface.
The first version is intentionally narrow and serious. It should feel like the beginning of institutional memory, not like marketing content wrapped around a search box.
Meaning-level retrieval
Search by concept, mechanism, or adjacent diagnosis without depending on exact keyword luck.
Collections and exports
Shared collections, citation metadata, and export paths so community members can work from the same source of truth.
Operator-ready infrastructure
Edge deployment, low maintenance overhead, and a handoff path if your team wants to own the portal directly.
Access model
Three ways to get the portal into the world.
The decision is operational, not aesthetic: move fast with a founding lane, own the system outright, or have Revasser keep it running with you.
$497
The fastest path: one condition, one deployment, one working session. Built to get a community from scattered papers to a real portal without ceremony.
Best for: advocacy groups that need proof in public before they budget for a broader rollout.
$997
Codebase, deployment guide, and operator handoff. Your organization owns the portal and runs it in your own account.
Best for: teams with technical support that want the infrastructure, not the service layer.
$7,500
Revasser deploys, tunes, and maintains the portal. Fastest path from literature sprawl to a durable flagship resource.
Best for: foundations and communities that need the portal live without taking on maintenance debt.
Direct close
Name the condition. We’ll decide the right deployment lane from there.
If the literature is scattered, the portal is the fix. Start with the condition and the community reality. The rest is implementation detail.
Send the condition, what the community needs most, and whether the priority is speed, ownership, or managed continuity. That is enough to decide whether the founding lane, owner-run build, or managed deployment is the right move.
No discovery workshop. No fake pipeline. Just the shortest path to a research home that deserves to exist.