50GRAMx Sites

Sites.

Publishes a website from a folder or a build, and serves it from your own grams with the network’s edges in front.

  • Every version is a signed record
  • Your domain, proven by DNS
  • No cookies, no tracking script
  • Copies on up to 3 of your grams
  • Roll back in one command
Does the job ofVercelNetlifyFirebase HostingCloudflare Pages
www.50gramx.com
The 50gramx.com home page, served by Sites
This site, served by Sites from the company’s own grams. Captured 16 Nov 2026.
In production
316,629requests served for 50gramx.com in a week, from one person’s gram7 days to 16 Nov 2026, epnd site list
5,518networks those visitors came fromsame reading
11,034files in one published version of 50gramx.comgram log, 16 Nov 2026
3member grams holding the company gramx in stepepnd site gramx show, 16 Nov 2026
See it for yourself →

Everything Sites does

All features

What you get

  • ✓A site that stays up while one machine is busy or off: copies sit on several grams.
  • ✓Each build is a version; going back is one step.
  • ✓No bill for bandwidth spikes from a cloud you do not control.

Why it is different

  • →The site lives on machines you own; edges only carry it to strangers.
  • →Hosting belongs to the gramx (the business), not to one person’s account.

Made forsmall businessesagenciesdevelopers

How it works

The whole flow
1You build2A gram takes it3It goes live4Copies spread5Edges serve6You see it

Start in a few commands

  1. 1. Publish the folder
    $ epnd site publish ./out --name shop
  2. 2. Bring your domain
    $ epnd site gramx domain-add shop.example.com --gramx <your-gramx>
  3. 3. Route it
    $ epnd site gramx route shop.example.com shop --gramx <your-gramx>
Read the quickstart
What a gram’s sites did this week
$ epnd site list
webtest2
  https://saturn-crux-50gramx-50.gramx.50gramx.com
  last 7 days: 316629 requests from 5518 networks, 17812.5 MB; 14% by bots and crawlers
  version ab44f052b217  (8387 files, 632.1 MB; 0 earlier kept)
fabric
  https://apogee-sagitta-50gramx-50.gramx.50gramx.com
  last 7 days: 72 requests from 15 networks, 1.3 MB; 12% by bots and crawlers
  version 743ca7401477  (2 files, 0.1 MB; 6 earlier kept)
Real output. Read on the founder’s Mac gram, 16 Nov 2026. webtest2 served 50gramx.com until it moved to the company gramx on 15 Nov.

Moving from another host?

The same build output (a static folder) you deploy today.

Questions people ask

All questions
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.

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.
Start with SitesThe same build output (a static folder) you deploy today.
Works with