Architecture Philosophy

SCAYLE Storefront Hosting is built around a few deliberate design choices. Understanding them helps you decide whether the platform fits your needs and what to expect from working with it.

Opinionated for Storefront Application

Storefront Hosting is purpose-built for SCAYLE's Storefront Application. It isn't generic application hosting. That tight coupling means everything from the build pipeline to runtime behavior to monitoring integrations is tuned for how Storefront Application works. The trade-off: you can't run arbitrary code, but you also don't spend time wiring up infrastructure for it.

Natively integrated with SCAYLE

Storefront Hosting isn't a separate product you connect to SCAYLE - it's built into the SCAYLE platform itself. Your hosting projects, shops, environments, deployments, and user permissions all share the same Panel, the same access controls, and the same operational conventions as the rest of your SCAYLE setup.

A practical consequence: because SCAYLE is multi-shop by design, Storefront Hosting follows the same model. Each shop has its own isolated Hosting setup - separate deployments, separate environments, separate domains, separate observability. Multi-brand businesses running several storefronts get clean isolation between brands without each one needing its own hosting account or infrastructure to manage.

Managed by default

You don't manage servers, networks, scaling policies, or cloud accounts. The platform does. This frees your team to focus on what makes your storefront unique - products, content, customer experience instead of operational plumbing.

Built on proven cloud infrastructure

Storefront Hosting runs on AWS, with managed in-memory caching via ElastiCache and edge delivery via Cloudflare. You get the reliability and global reach of these platforms without managing them directly.

Convention over configuration

Default settings are chosen to work for the majority of e-commerce storefronts. Where customization is offered (domains, environments, integrations), it's exposed through the SCAYLE Panel rather than through configuration files or infrastructure-as-code. This reduces the learning curve and the surface area for misconfiguration.

Security and observability are built in, not bolted on

Vulnerability scanning, script integrity monitoring, application logs, and metrics are platform features available the moment your storefront is deployed, not something you assemble from third-party tools. Native integrations with all major monitoring providers are available if you already have observability pipelines.

What this means for you

You ship faster and operate with a smaller team than self-hosting would require. In return, you trade fine-grained infrastructure control for opinionated defaults. For most e-commerce teams running on SCAYLE, this is the right trade.