Push code, Fabric ships it. Every release is a stored, exact artifact you can roll back to.
Bring the metal.
Get a cloud.
Apps, databases, backups, domains and private networking on servers you own. We run the control plane.
Your traffic
Your traffic never touches our plane.
The control plane sends instructions and reads status. Your data moves between your servers, encrypted, and your servers answer requests to your apps.
Traffic between your servers is always encrypted.
$ git push fabric main
$ fabricctl repos runs shop
build done
publish done
deploy Live https://shop.example.com
$ fabricctl app rollback shop
previous release Live, same images, no rebuild
Your releases
Push. It's live.
Changed your mind?
Connect GitHub or Fabric Code and every push builds on your own capacity and ships. Every release is kept, so rolling back takes seconds.
- Asked for, and runningEvery resource shows both.
- DNS, re-checkedDrift shows up as a state.
- Backups, rehearsedRestore drills check they recover.
Everything an app needs.
Available today unless marked coming.
Run and govern
Your capacity, your organisation, one Console and CLI.
- Capacity
- Organizations & projects
- Secrets
- Console & CLI
- Inferencecoming
- Machinescoming
Who owns what
We run the plane.
The Console, sign-in, generated addresses and certificate renewal. Never your pager.
You own everything else.
Servers, apps, data, domains, secrets and history belong to your organisation, even on granted capacity.
We run our own business on Fabric: emberconsult.com is served from our own servers today.
Bring your metal.
Fabric is in early access, by invitation.