Skip to main content
SynaptaGrid Platform
← All capabilities
Available now

Platform capability · Frontend Hosting & Deployment

One frontend build for every customer

One build, with each customer’s settings loaded when the app starts

The platform serves one frontend build behind a global CDN. The build contains no settings. When the app starts, it loads the customer’s settings based on the hostname in the request. The hostname mapping at the edge, the public start-up endpoint, the CDN and origin component and the operator’s deploy action are all part of the platform.

Built in

What you get

  • One frontend build serves every customer, with no settings inside it
  • The edge maps each hostname to the right platform deployment
  • A public start-up endpoint gives the app its customer’s service addresses when it loads
  • A reusable CDN component: files are served with cache headers, and the origin accepts requests only from the CDN
  • Operators deploy from the operator console
  • The same build serves customers on a shared subdomain and customers on their own domain
  • Each frontend deploys from its production branch through its own pipeline
  • Branding and theme are loaded for each customer when the app starts, with no rebuild
Under the hood

How it works

Customer settings are loaded from the request hostname

When settings are built into a frontend, each customer needs a separate build, and every settings change needs a new deployment. Here the frontend is built once with no settings inside. The edge maps the incoming hostname to the right platform deployment. When the app starts, it fetches its customer’s service addresses, branding and feature switches from a public start-up endpoint. A changed setting takes effect the next time the app loads, with no rebuild and no new deployment.

One build for shared and dedicated customers

A customer on a shared subdomain such as acme.yourplatform.com and a customer on its own domain such as app.acmecorp.com are served by the same build. The difference is the host record and the answer from the start-up endpoint. A dedicated deployment gets its own host and separate data infrastructure, and the frontend code stays the same.

How a frontend is deployed

The pipeline component, the hostname mapping, the start-up endpoint and the operator’s deploy action are in place. Each frontend deploys from its production branch through its own pipeline. Pairing a dedicated frontend with a dedicated app follows the dedicated app deployment work.

Further additions

Additions that extend the capability described above.

  • Pairing a dedicated frontend with a dedicated app deployment (follows the dedicated app deployment work)
Pairs well with

Related capabilities

Multi-tenancy

Checks on every request, a separate database, or dedicated infrastructure

Customer Portal & UI Kit

White-label customer portal, connected to the platform

Organizations, Plans & Settings

One record of every customer, app, plan and setting, with overrides for each customer

Want a deeper walkthrough of Frontend Hosting & Deployment?

A solution architect will demo the live service against your domain model.

Get a deployment assessment