Environments

An environment is a server where you host your projects and run production data.

In Flowize, you usually build and test your implementation in the Designer. Once the project is ready, you move it to an environment so it can run with real data, production settings, and dedicated server capacity.

Environment vs. Project

A project is where you organize your flows, storage, triggers, apps, contents, and conditions.

An environment is where that project runs in production.

In simple terms:

• A project contains the logic and configuration.
• An environment provides the server that executes that project.

You can host one project in one environment or run multiple projects in the same environment if the package and server capacity fit your workload.

Why environments matter

Environments let you separate building from running:

• In the Designer, you configure flows, interfaces, apps, contents, and test data.
• In the environment, you run production data.

This separation is useful because production workloads need stable infrastructure, predictable performance, and their own operational settings.

What an environment includes

When you create an environment, you choose the server characteristics that will support your workload:

• A package, which affects storage and performance
• A region, which affects where the server is hosted
• A timezone, which affects time-based behavior such as schedules and date operations

Once the environment is ready, you can host projects in it, update them, review logs, and configure items such as URL mapping or SSL certificates.

For URL mapping, domain DNS settings, and certificate upload or removal, see Custom domains and SSL certificates.

For software updates, recurring maintenance, progress monitoring, and recovering free storage space, see Environment updates and storage optimization.

For server package upgrades, additional storage, and scheduled capacity changes, see Increase environment capacity.

For pausing or resuming background processing, recording a pause reason, and searching environment activity, see Worker controls and environment logs.

For public or private environment access and managing selected organization members, see Environment access management.

Designer vs. Environment

The Designer and an environment are related, but they are not the same thing.

Area	Main purpose
Designer	Build, configure, and test your implementation
Environment	Host projects and run production data

The Designer is the workspace where you prepare your project. The environment is the server where that prepared project is deployed and executed.

When you need an environment

You typically need an environment when:

• You want to run real production data
• You need better performance than the shared Designer execution
• You want a dedicated server setup for hosted projects
• You need production endpoints such as API, frontend, or web endpoints

Summary

An environment is the production server layer of Flowize. You build your solution in a project inside the Designer, and you use an environment to host that project and execute it with production data.

If you want to learn how to create, configure, or update one, read How to create an environment.