Setting up In House Fuuz

Setting up In-House Fuuz

Article Type: Configuration / How-To Audience: End Users Module: Fuuz Platform

1. Overview

What is Fuuz In-House? It is essentially the same software that is used in the cloud, but accessible for on-prem/localized deployments. Some licensed features are excluded from In-House deployments and are only accessible from the Cloud version. Additionally, some of the key components used in the cloud for high availability/redundancy are also excluded, as they are not supported in Docker Swarm.

This article explains how to set up your Fuuz In-House Trial. If you have not yet submitted for a license, do so here and fill out the required information. The license will then be delivered to the email you provided on the form, from mail@admin.fuuz.app.

The Fuuz In-House Trial is delivered through a Portainer Template on the Portainer Template Store.

2. Prerequisites

1. System requirements
   1. You must have admin privileges on the machine, or have an IT group that can assist you.
   2. Docker must be installed on the target machine.
      • We recommend Docker Desktop for its easy management if you aren't familiar with containerized environments and command lines.
   3. Minimum requirements — at this spec you will likely have issues when the app grows in size or you run multiple apps concurrently:
      • 8 GB of RAM
      • Quad-core CPU
   4. Recommended requirements:
      • 32 GB of RAM
      • Octa-core CPU
2. A license provided by Fuuz

3. Steps

1. Install Docker Desktop for your operating system (instructions).

2. From an elevated command line, execute docker swarm init.

   • This provides the ability to run Docker in swarm mode.

   Important: If this command isn't executed successfully, you will not be able to successfully provision the template.

3. Install the Portainer extension for Docker Desktop:

   1. From Docker Desktop, navigate to the Extensions tab on the left panel.
   2. Search "Portainer".
   3. Click Install.
   4. Once installed and running, by default Portainer is accessible from https://localhost:9443.
      • By default this runs as an HTTPS server but does not have a valid certificate. Follow the instructions in your browser to ignore the warnings.
      • We recommend signing up for the Business Edition for free, which provides the ability to deploy Portainer on up to 3 separate nodes (this deployment uses only one).
   5. Set up your username/password.
      • Save these somewhere to ensure you don't lose access in the future.

4. Inside Portainer:

   1. Navigate to Templates.
   2. In the search, look for Fuuz In-House.
   3. Fill out the required prompts.
   4. Press Deploy. The stack will immediately start provisioning the following:
      • Mongo database
      • RabbitMQ message broker
      • Running the initial seeds to get the environment up and running

5. From this point forward, interface with the running stack under the Stacks tab on the left side panel.

   • By default all services run as a single container to support minimal resource use. If you have extra capacity on the hosting machine, you can tinker with the number of replicas of each service. The services below provide the largest benefit from scaling:

   Service	Benefit of scaling
   Application	Provides redundancy for the Application GraphQL API and allows requests to be distributed across pods. Good for a high volume of writes.
   Orchestration Worker	Provides additional concurrent flow node executions.
   Transformation	Provides additional capacity for Fuuz Scripting. Scale this similar to the Orchestration Worker, as additional node executions will require additional Transformation capacity.
   Data Change Capture	Provides more concurrent Data Change Document writes. Scale this in accordance with the volume of Application GraphQL API requests to flush the buffered messages in RabbitMQ faster.
   Integration	Provides higher availability for high-volume external integration requests. Scale this in accordance with the number of connections/requests.
   Router	Provides a gateway between the frontend and the backend. Scale this in accordance with the number of requests made to the API from outside of the Docker network (frontend, external API requests).

4. Validation / Success Criteria

• The stack comes up and is accessible on the local domain you provide (the default is fuuz.localhost).
• Log in with the information provided in the email:
  • Email used to sign up
  • Password defaults to Welcome1
• If login was successful, you're all set! From here, we strongly recommend watching the Get Started videos (the link is on the home screen).

5. Resources

• Getting Started
• Support
• YouTube

6. Troubleshooting

My license says it's expired, but I know it's valid.

• Verify you didn't add any characters before or after the license key.
• Copy the license key fresh from where it was provided and try to inject it again.
• If none of the above solve the problem, reach out to sales@fuuz.com with the following so we can troubleshoot:
  • Send the email from the address that was used to create the license (the seed user account).
  • The License ID (provided in the initial welcome email for the license).
  • The current container image/tags (if you aren't using latest).

Most of the /fuuz container images shut down shortly after I deploy the stack, but the license server stays up.

• This usually indicates your license has expired. Check the container logs to confirm. If you would like to extend your license, please reach out to sales@fuuz.com.

I can't reach the frontend from fuuz.localhost from another machine.

• This local domain will only resolve within the context of the machine it's hosted on.
• If you would like to access it more broadly on your home network, some routers support local DNS record redirects. If your router doesn't, consider something like Pi-hole to provide a local DNS server for your network, where you can map any local URL to the server/API.
• If you would like to access it from outside your network, options include Tailscale (currently free for up to 3 users/100 devices) and Cloudflare Tunnel (free if you already have a domain on Cloudflare).

7. Revision History

Version	Date	Editor	Description
1.0	2026-02-13	Fuuz Documentation Team	Initial Release

See Also

• Trouble-Logging-Into-Fuuz
• Switching-between-Fuuz-Environments-Build-QA-Production
• Logging-into-Fuuz-–-Cloud-Access
• Recovering-Your-Fuuz-Account

---

Source: support.fuuz.com