Finance and accounting decision
StellarID
A competent developer can build a basic hosted Stellar federation resolver and dashboard, but the full hosted product experience (scale, polished UX, support, and reliability) is nontrivial, so building a minimal replacement is realistic while replacing the paid service entirely is borderline.
Visit website↗Built by François Rejeté, who ships 6 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off56 h to build
$10/mo4 h/mo upkeep
No published price to break even against.
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
- Resolve federated Stellar addresses, register address mappings, expose federation HTTP endpoint, collect and display federation query logs, publish stellar.toml guidance for domains
What it still won’t have
- Hosted uptime, scaling, and SLA
- Polished UX and onboarding
- Customer support and issue escalation
- Operational monitoring and hardened security configuration
- Any proprietary analytics or usage dashboards provided by the vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
StellarID does not publish a price we could read, so there is nothing to compare against. What building costs is below.
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 self-hosted Stellar Federation service using Node.js (Express) for the API, Postgres for storage, React for a small admin dashboard, and Docker for deployment. Scope: implement the Stellar federation HTTP endpoint (resolve name*domain → account ID), a REST CRUD API to manage address mappings, authenticated dashboard to add/edit/remove mappings, logging of federation queries with a searchable UI, and documentation/automation to publish a stellar.toml file for the customer's domain. Out of scope: paid plans/billing, multi-tenant billing, complex analytics, and managed SSL (use Let's Encrypt). Include input validation, sensible error handling, unit and integration tests for the resolver and CRUD API, Dockerfiles, and a deployment guide for a VPS (systemd) or container host.
How we checked
How the score was reached
- Partly verdict base52
- 4 cited sources+3
- Evidence score55
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 · 4
Every page the run actually retrieved.
- official productStellarID.io
- official productStellarID.io - service description
- official productStellarID.io - logs
- official productStellarID.io - reverse federation
Integrity checks
What held up, and what did not.
