Agencies
Run every client site from one panel, on special partner pricing, and take a share of every site you bring. We never contact them.
Thebes Hosting
A site that cannot be taken down.
Your site runs as a contract on the Thebes chain. There is no server to patch, no plugin to break, no host that can lock you out, and nothing to get hacked between invoices. 700 EGP a month, or 6,000 EGP a year, per site.
Who it is for
Three ways people use this.
Freelancers
One price per site and nothing to hand over but a login. No hosting account to set up, nothing to maintain after the invoice clears.
Partners
Building on the substrate, or reselling it at volume. Terms are written per partner rather than picked off a list.
What you stop doing
No backups. No passwords. No disaster plan.
Nothing to back up
Your site is not a copy sitting on one machine. It is replicated across the network as it runs, so there is no nightly job to configure, no snapshot to pay for, and no single disk whose failure costs you the site.
Sign-in is already built
Biometric passkeys ship with the platform, working today. Your users sign in with the fingerprint or face they already use on their device. You store no passwords, so you cannot leak any.
No separate database to wire up
Every node runs the same code over the same state and reaches the same answer. Not static files with a database somewhere else: the full stack, backend included, executes on the network.
Recovery that cannot fail with you
Ordinary disaster recovery is a second system that tends to die in the same disaster: backups on the same provider, a failover in the same account. Here recovery is not a system you switch to, it is how the network runs. It is Byzantine fault tolerant, so it keeps agreeing on the right answer even when part of it is not merely offline but wrong.
Underneath the hosting
Built for records that have to hold.
Hosting is what most people buy. Underneath it is a settlement layer: the same network settles payments and holds registries, and the reasons it suits that work are the reasons a site on it stays up.
Final in under a second
A payment is settled when it says it is settled. There is no waiting for confirmations to stack up, and no window afterwards where it can quietly reverse.
Interoperability without a bridge
It reaches other chains through its own threshold signing, producing signatures in the schemes those networks already use. That is what makes it interoperable with other chains generally rather than a chosen few, with no bridge and nobody holding the money in between, so a cross-border payment is one transaction that carries its own audit trail.
Nothing to back up
Every machine on the network keeps the whole record, in step with the others. There is no backup to schedule and nothing to restore, and losing machines does not take the service down with them.
Custom financial deployments
Institutions rarely want the standard product. A deployment is specified around the rules you work under, the roles and approvals you already have, and the reporting you are required to produce, and it runs on the same network rather than off to one side.
Where that matters
Payment instructions, securities, land titles and court records are signed once and then read for decades. They have to stay available without depending on one data centre, and stay provable long after today's encryption stops being enough.
For institutions
Deployed on your terms, in your jurisdiction.
A custom enterprise deployment is not the shared network with a different invoice. It is your own nodes, your own terms, and a set of standards your systems already speak.
Data residency, guaranteed
Nodes are deployed into regulated data centres in Egypt and across the region, so your data stays in the jurisdiction that regulates you. Deploy in Egypt and it stays in Egypt. Deploy in the Gulf and it stays there. For an enterprise deployment the nodes can run in your own facility.
Written per organisation
Terms are written per organisation rather than picked off a list, with a response time set in the agreement. We publish none by default. Invoicing is on your terms, and there is a named person to reach.
Delivery versus payment
Both halves of a trade, or neither. Cash and asset move in one indivisible step, so there is no moment where one side has delivered and the other has not.
The standards you already run
ICRC-1, 2, 3, 7, 10 and 37 are implemented, along with ISO 20022 camt and pacs messages, so a settlement reaches your existing systems in the format they already read.
Proof, not only a report
Every settlement carries a cryptographic proof rather than a line in a statement, and the exchange source is public, so your auditors can read it before you commit to anything.
Migration of a whole estate
Moving one system is a pilot. Moving an estate is a plan, made with you, with the order of migration and the fallback at each step agreed before the first system moves.
Moving in
We move your existing site. Free, in 24 hours.
Content, media, routes and both languages come across, and your old URLs keep working, so the rankings you already have survive the move. You approve a staging URL before anything changes.
The clock starts when we accept the site and you have given us access, and stops when the staging URL is live for you to review.
The panel
Deploy from a browser tab.
Pick a template, edit it, check it, deploy it. No local toolchain, no server access, and no shared password: everyone signs in with their own passkey.
