# Architecture and Deployment > Run Fuuz in full cloud, two-tier or three-tier deployments, Fuuz-hosted on AWS or Microsoft Azure or in your own data center, with edge gateways at each site. Source: https://www.fuuz.com/platform/architecture Architecture and deployment Fuuz runs in full cloud, two-tier or three-tier deployments. Any tier can be Fuuz-hosted in public or private cloud on AWS or Microsoft Azure, or run in your own data center. Every option runs the same platform and applications, from one site to an entire enterprise. [Design a solution](https://www.fuuz.com/contact) [Compare options](#deploy) Deployment options ## Deploy Fuuz The Way Your Enterprise Runs Every option runs the same platform and applications, and every deployment includes build, QA and production environments. Choose how your sites connect, then choose Fuuz-hosted or your own data center for each tier. Data connectionFuuz-to-Fuuz syncFuuz drives or controlsFuuz GatewayOptional Option 1 ### Full cloud Fuuz-hosted public or private cloud, or your own data center Fuuz runs as one enterprise that people, sites and business systems connect to directly. - Hosting: Fuuz-hosted public or private cloud on AWS or Microsoft Azure, or your own data center - Gateway: not required; add one when integrations run inside your network - Structure: one Fuuz enterprise Option 2 ### Two-tier Fuuz-hosted public or private cloud, or your own data center, with gateways at your sites Fuuz Gateways at each site connect equipment and on-premises systems and feed one Fuuz enterprise shared by every site. - Hosting: Fuuz-hosted public or private cloud on AWS or Microsoft Azure, or your own data center - Gateway: Fuuz Gateways on premises at each site (common, not required); topics on edge connections form a local UNS that is visible in the Fuuz enterprise - Structure: many gateways feeding one Fuuz enterprise - Offline: gateways buffer data locally; expect 4+ hours, depending on implementation Option 3 ### Three-tier Fuuz-hosted public or private cloud, your own data center, or a mix Each plant or warehouse runs its own Fuuz enterprise in the site tier, fed by gateways in the edge tier. Site-tier enterprises roll up to a Fuuz enterprise in the central tier. Every tier runs the same platform. - Hosting: any tier can be Fuuz-hosted or run in your own data center - Gateway: one or more per site (common, not required) - Structure: edge tier (gateways), site tier (a Fuuz enterprise per site), central tier (one Fuuz enterprise) - Offline: each site runs on its own for as long as it needs, then synchronizes Reference deployment architecture ## How The Tiers Fit Together A closer look at the three and two-tier options: what runs in each layer, and how the layers connect. Site and gateway names are examples. Three-tier ### Three-tier reference deployment An enterprise layer in a private cloud, a site layer with an application gateway installed per site, and edge gateways line-side. Each site keeps local control of its critical operational applications, and the sites connect up to the enterprise layer over HTTPS through a site-to-site VPN. Fuuz applicationsFuuz GatewayTwo-way connectionSite footprint Two-tier ### Two-tier reference deployment The enterprise layer runs the enterprise apps and every site's applications, and edge gateways connect each site's equipment to it over HTTPS through a site-to-site VPN. Fewer layers to operate on the same platform. Fuuz applicationsFuuz GatewayTwo-way connectionSite footprint Hosting ## Fuuz-Hosted Or Your Own Data Center Every tier of every option can be hosted by Fuuz or run in your own data center. Here is what changes. Your own data center - You host and operate the infrastructure - You apply platform updates and patches - You monitor security and resources - Fuuz service level agreements do not apply Fuuz-hosted (public or private cloud) - Hosted on AWS or Microsoft Azure - Updates and patches delivered by Fuuz - The latest updates and enhancements arrive nightly in your build environment - Production environments are updated monthly - Security monitoring, resource monitoring and optimization - Fuuz service level agreements and premium support options Included in every deployment ## Same Platform, Same Discipline ### Build, QA and production Every deployment includes build, QA and production environments, so every change follows the same governed path. Additional build or QA environments are optional. ### Self-updating gateways Fuuz Gateways support automatic updates, so edge connectivity stays current without site visits. ### Scale by adding sites Add gateways to a Fuuz enterprise, or add sites to the site tier of a three-tier deployment, as the business grows. Layers ## How The Platform Is Built ### Edge The Fuuz Gateway connects equipment with outbound connections only and buffers through network drops. ### Platform Event-native services, the data store, modeling, ORM and the GraphQL API. ### Applications Accelerators and the applications you build, all reading from one model. ### People and agents Users and AI agents on any modern browser, governed by one access model. How do these layers line up with the new industrial AI stack? [See where Fuuz fits](https://www.fuuz.com/platform/industrial-ai-stack). Built to scale ## One Site Or Hundreds ### Isolation per enterprise Each enterprise has its own database, and each tenant has its own data model, so your data is never mixed with other customers'. ### Always current when Fuuz-hosted Fuuz-hosted build environments receive the latest updates nightly, and production is updated monthly, without upgrade projects. ### Nothing to install Applications run in current versions of Chrome, Edge, Firefox and Safari. Get started ## Ready To Run Every Operation As One? Tell us what you run today and what you need next. We will map how Fuuz fits, without ripping anything out. [Start the conversation](https://www.fuuz.com/contact) Prefer to talk? Call [1-877-801-FUUZ (3889)](tel:18778013889)