You run a business. We run the machines.
Everything below is what actually happens, in order, with nothing left out.
The ten minutes
- 01Name it
You pick a company name and an address. It goes live immediately at you.site.nodeshop.app — no DNS, no waiting.
- 02Choose chains
Pick the networks you want to sell. One credit allowance spends across all of them.
- 03Set prices
Three plans are priced for you at a 60% margin. Change the middle one and the others follow.
- 04Design the page
A headline, a colour, and a live preview. Published the moment your company exists.
- 05Save your work
One email, one code. The account is the last step, not the first.
What you get, concretely
Drag your plans, chains and endpoint sample onto as many pages as you like. Publish per page.
Point a CNAME at us and the certificate is issued on the first visit. Your platform address keeps working meanwhile.
Your customers get keys, usage, limits, invoices and support — all under your name, never ours.
The builder computes wholesale cost live and refuses to publish below it.
Settlement is per period, on what you actually collected, minus wholesale and our cut.
Your customers reach you. When the problem is infrastructure, it becomes ours.
What your customers see
They land on your page, choose a plan, pay, and get a key. Their first request looks like this — against your address, never ours.
curl https://you.site.nodeshop.app/rpc \
-H "Authorization: Bearer $THEIR_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"getSlot"}'When something breaks
- A node is degraded
- Ours to fix. Capacity is rerouted, and the status page says so before you have to ask.
- A customer's key stops working
- Yours to answer, ours to diagnose. Every key, request sample and limit is visible in your console.
- A payment fails
- The customer is told, retried, and given a grace period before access changes.
- We have an incident
- It appears in your console and on the status page. You are not the last to know.