Many sites.
One source of truth.
Run each brand as its own project, or feed several sites from one. Your people sign in once, every site is served from the nearest edge, and a shared change is live everywhere in under three seconds. Press Publish and watch.
- Osteria LumenOpen daily, 8:00 to 22:00Cached
- Lumen BakeryOpen daily, 8:00 to 22:00Cached
- Lumen ShopOpen daily, 8:00 to 22:00Cached
A project per brand,
or one for all of them.
Brands with their own teams and their own models get their own projects. Sites that share products, people or legal copy read from one project, each through its own key. Choose per brand.
- ProjectOsteria LumenOwn models, people, keys
- ProjectLumen BakeryOwn models, people, keys
- ProjectLumen ShopOwn models, people, keys
- Siteosterialumen.comReads its own project
- Sitelumenbakery.comReads its own project
- Siteshop.
osterialumen.comReads its own project
Each site reads
only what it shows.
Give every site its own key, limited to the models it renders and the origins it runs on, with an expiry. Rotate one site’s key with a grace window and the other sites never notice.
- Osteria Lumen siteRead · Menus, Pages, Settings
cap_live_…3f2a - Bakery siteRead · Breads, Pages, Settings
cap_live_…7c90 - ShopRead · Products, Settings
cap_live_…e21b
One login,
the right brands.
People sign in once and see the projects they belong to. Give each brand team Content on their own site, your central team Admin everywhere, and an outside writer a single model on a single brand.
Writes and publishes for the bakery. Reads the shared legal copy.
- Osteria LumenNo access
- Lumen BakeryEdit and publish
- Lumen ShopNo access
- Shared legalRead only
Every brand,
served from cache.
Published content is served from the nearest of Fastly's edge locations, typically in 20 to 50 ms, whichever site asks. A publish purges only the entries and models it touched, so one brand’s launch leaves the others’ cache alone.
A request log: reads answered from the edge cache, typically in 20 to 50 ms, and a publish that purges only the keys it changed.
Every brand,
one place to run it.
Start with one site for free. Talk to us when the whole group is ready to move.
More ways teams use Capa
- DevelopersAPIs, agents and an SDK you will like→
- Marketing teamsShip pages without waiting on a deploy→
- AgenciesOne login for every client you run→
- Content editorsEdit what you see, publish when it is right→
- E-commerceProducts, reviews and stories in one place→
- Apps & every screenWeb, mobile and anything that reads an API→