Each one is its own product, metered on the same few units and signed by the machine that did the work.
Running for customers today.
Publishes a website from a folder or a build, and serves it from your own grams with the network’s edges in front.
Keeps files and objects on your grams, each one addressed by its content, with copies placed on more than one machine.
Runs open AI models (text, speech, vision) on your grams, with every answer signed by the machine that made it.
Opens your home or office machine from anywhere, with no router ports opened.
Every answer and every number is signed by the machine that produced it, and anyone can check it.
Working on our own grams; open to early users first.
Connects a domain: DNS records, certificates and the route to the right site, set up in one flow.
Counts a site’s visitors, pages, sources and errors at the edge, with no script on the page and no cookies.
Backup: every version kept for a set time, copies in more than one place, restore from any device.
An in-memory store (Redis) for fast lookups, sessions and model caches, shared by the work on a gram.
Meters every piece of work, signs a receipt for it, and settles what each gram is owed.
Runs an app or a container on your grams; ask Evo in words and it writes the operator for it.
Runs a small program when it is called or on a schedule, asleep the rest of the time.
Keeps keys and secrets sealed to the gramx’s grams, lent to the operators that need them, never copied by hand.
A closed room where an agent runs code: no host access, nothing it was not given.
Work runs on your own device first, then a nearby gram, then a cloud, in that order.
One gramx for an agency’s clients: their sites, domains, backups and traffic in one place.
Designed and planned. Join the waitlist to shape them.
A database that runs on your own grams, keeps working offline and syncs when the network returns.
Lets people sign in to your app with keys they hold, no passwords to store or leak.
Sends a business’s email (receipts, sign-in links, newsletters) and keeps its mailboxes on its own grams.
Reaches a person on their own devices: alerts, messages, reminders.
Git hosting on your own grams: every repository kept on at least three of them.
Holds container images on your own grams, so apps start with no outside registry.
Logs, errors and uptime for everything a gramx runs, including the devices that are offline.
Search by meaning over your own files and records, without uploading them anywhere.
Phones and tablets hold copies of the gramx’s data and serve them, putting storage people already own to use.
You choose which devices, and so which countries, hold your data.
Shops, clinics and offices keep working offline and sync when the line comes back.