The Fuuz Platform, is cloud based, of course. Presently it is hosted in the AWS (Amazon Web Service) atmosphere. Maybe you’re wondering, why there versus somewhere else.

Amazon is agnostic, just like Fuuz. Apposed to something like Azure, which would create limitations on how we construct Fuuz or what Fuuz is able to do, we wanted to have something more flexible.

Not only Flexibility, but Amazon is the largest, most robust and most trusted cloud on the globe. With well over 50+ points of failover across their twisted web of datacenters globally, we know, and now you do as well, that your data is always safe, and the solution (knock on wood) is always running. When people can’t watch their Netflix, they get upset, that’s why Netflix and most other serious cloud players have selected AWS as their system of choice.

Enterprises

Fuuz, as mentioned is an Enterprise Mesh Architecture.

You may have heard about something called “multi-tenant” this was the go to model for cloud software vendors for the past 2+ decades. However, due to cybersecurity risks and many of those legacy systems being hacked - what we learned from that is keeping everyone’s data in a single spot, introduces risk.

Fuuz is different, Fuuz architecture includes a centralized service mesh that’s used by all of our customers, for standard features and functions to provide the scalability of the cloud to our customer base. However, when it comes to data, or specific apps - those are enterprise, or customer specific services. This unique design, is how and why our solution can be so flexible for all of our customers. It is also what enables the Fuuz Platform to address regulatory requirements, provide customers to create custom fields and tables, unique screens, etc. In addition, our customer’s data, resides isolated rather than being intermingled with all other customer data. Just imagine, how much more secure that is for you compared to the old method of placing your sensitive data along with everyone else.

As a user of the Fuuz Platform, you will have an Enterprise. Your enterprise is designated by the URL (or web link) to your site, under typical circumstances your business domain (or think of this as your companies website address) is used as a subdomain on the Fuuz platform.

Eg. If your business is ACME Manufacturing and your website is www.acme.com; your Fuuz Enterprise subdomain would be http://acme.fuuz.app

Tenants

Within the world of an Enterprise on the Fuuz Platform, there are multiple Tenants. Each Tenant provides additional data isolation. This allows our customers to segregate between business units, physical locations, etc. Really, this can be setup however you want it to be, to support your business model. This can also be changed down the road, should things change for you.

An Enterprise can support any number of Tenants. So it does not matter if you have 1 location, or 10,000 locations - these would all be Tenants within your Enterprise. In some cases, larger companies will setup an Enterprise for a particular business unit. Perhaps you have 3 business units. One of those is your production operations, another is your aftermarket and the last is your distribution. Each business unit, may have several sites or locations involved with it, so you may desire to have a setup more like this:
acmedist.fuuz.app

acmeprod.fuuz.app

acmeafter.fuuz.app

Within each of these Enterprises, then would reside the individual physical locations, setup as unique Tenants.

Considerations to take into account, when deciding whether you need separate Tenants on the Fuuz Platform:
1. Timezone; if operations take place in different time zones, you should have separate Tenants

2. Currency/Localization/Language; if you have language differences, currency or localization needs you should consider separate Tenants

3. Operational; if your operations vary widely between locations, as in one location is discrete, another is process and another is batch, you may want separate Tenants

4. Ease of Use; separate Tenants can often be easier for a smaller IT team to manage, in terms of users and security, who has access to see and/or manipulate what data can be more complex in a single Tenant

5. Costs; Tenants do add additional cost to your Fuuz contract

6. Portals; if you’re looking to introduce Customer or Supplier, or even Employee facing portals, these often times should be their own Tenant

7. Integrations; if you’re environment includes multiple ERP systems that you need to connect to Fuuz, generally 1 ERP to a Tenant is preferred, other options exist, but introduce unnecessary complexity

Access to your various tenants is on the bottom right corner of your Fuuz site, the displayed Tenant - refers to the current tenant that you’re working in; you can click the section and see other tenants that you have access to:

Environments

The basic concepts of the Enterprise and Tenant setup apply to the different Fuuz Platform Environments that you may have access to.

What do we mean by environment? Well. An Environment, is an instance of Fuuz that has a specific purpose. Currently there are (3) Three different types of environments and you have access to 1 or more of them, depending on your Fuuz contract.

Production

Everyone is going to be familiar with the Production Environment. You can identify the Production environment once you’re logged into the system in the ‘tray’, we’ll show you what this is all about later on.

Additionally, Production is the only environment that doesn't have anything extra in the URL aside from your company website address as we mentioned in the earlier pages.

This Production environment, is where you perform, the real production transactions, any integrations with other systems, including emails, reports, etc. are all in “live” mode. The Production environment is updated once a month, with the latest platform enhancements, so you can be certain that they’ve all been tested thoroughly since they’ve passed through Build and QA first.

URL: [yoursite].fuuz.app

You can see in the bottom right corner of your Fuuz site - that you’re in “production”

QA

QA is short for Quality Assurance environment. This type of environment is used by our larger customers to perform UAT or user acceptance testing, of various applications and enhancements that we, partners or your teams maybe making to your applications within Fuuz. This is really helpful, so that you can be testing and validating, or even training new hires, without impacting Production, also you’re not impacting your technical teams from continuing to make enhancements to the system because they have their own special environment. This prevents anyone on the team from stepping on other’s toes, provides streamlined testing and validations so if you’re in a rapidly evolving business, who’s always looking to improve and progress, you likely want to have a QA environment to access long term.

The QA site, is updated with the latest and greatest Platform enhancements (remember like the operating system on your smart phone) every couple of weeks.

if you have a QA environment; you will access this by navigating to QA.[yoursite].fuuz.app

Build

Last but certainly not least is the Build Environment. Build is, where things get built. This is where teams of really creative people will work on building the perfect solutions to all of your business challenges. Build is updated every night, with the latest and greatest code from our engineering team, this allows your teams, or our partners to explore any new features; determine whether or not they’ll be useful to the business and then implement them to be tested by the larger teams.

URL: build.[yoursite].fuuz.app

You can see in the bottom right corner of your Fuuz site - that you’re in “build”