50GRAMx Sites

Questions people ask.

About Sites: what it does when a machine is off, domains, frameworks, moving over and cost.

›What happens if the machine holding my site is switched off?

The edges keep serving what they have cached, and fetch anything else from another gram that holds a copy. That is why a site should have more than one holder: add a second gram to your gramx, or let your own other grams hold it.

›Can I use my own domain?

Yes. You add one TXT record to prove the domain is yours and point it at the gramx. The gram checks for the records every minute and the edges start serving as soon as they see them.

›Does it work with Next.js, Astro, Hugo or plain HTML?

Anything that builds to a folder of static files. 50gramx.com itself is a Next.js static export of about 11,000 files. Server-side rendering on request is not offered yet.

›How do I move from Vercel or Netlify?

Keep your build. Publish its output folder, or point the site at where your CI uploads the build, then move your domain’s records. The move guides walk through each one.

›What does it cost?

You pay for the bytes your sites serve, at the meter rates on the pricing page, and you can set a monthly ceiling. Bytes served from your own grams are credited back to you.

›Who can see my visitors?

Only the owner’s gram receives the counts. Edges keep totals, not addresses, and set no cookies.

Start with Evo

Evo works on your own gram, with your machines in view, and asks before every change. Take one of these to it, or write your own.

  1. 1. Run a gramOn a machine you have. Evo lives there.
  2. 2. Enter your gramxYour business on the network.
  3. 3. Ask EvoPaste the question; it works through it with you.