Getting Started

Projects & Workspaces

Projects and Workspaces are the foundation of how you organize your work in Fimaflow.

A Workspace is your collaborative environment. It contains your team, members, billing, settings, AI credits and every project your organization owns.

A Project contains everything required to build, manage and deploy a backend application.

This separation makes it easy to organize multiple applications while keeping permissions, resources and collaboration centralized.

Demo placeholderOrganizing workflows across projects and workspaces

Workspaces

A Workspace represents your organization inside Fimaflow. Each Workspace has its own:

• Members and roles
• Billing and subscription
• AI Credits
• Projects
• Shared resources
• Deployment settings

You can create multiple Workspaces to separate personal projects, client work or different organizations. For example:

Workspaces

Personal Workspace
├── Portfolio API
├── Blog Backend
└── AI Playground

Acme Inc.
├── Customer API
├── Internal Dashboard
└── Payment Service

Every Workspace has its own permissions and resources.

Projects

A Project represents a complete backend application. Inside a Project, you can create everything required to design, build and deploy your backend. A project can contain:

• Multiple workflows
• API endpoints
• Database resources
• Environment variables
• Authentication
• AI nodes
• Deployments
• Generated exports

Each project is completely isolated from the others.

Creating a Project

To create a new project:

1. Open your Workspace.
2. Click New Project.
3. Enter a project name.
4. Choose an optional description.
5. Create the project.

Once created, you'll be taken to the Visual Builder where you can start designing your backend.

Organizing Workflows

Projects can contain multiple workflows. Each workflow should represent a specific business process. For example:

Project

E-Commerce API
├── Authentication
├── Products
├── Orders
├── Payments
├── Inventory
└── Notifications

Splitting your backend into multiple workflows makes large applications easier to understand and maintain.

Collaboration

Invite team members directly to your Workspace. Depending on their role, members can:

• View projects
• Edit workflows
• Manage deployments
• Configure environment variables
• Export source code
• Manage Workspace settings

Permissions help protect production projects while enabling collaboration across your team.

Project Settings

Every project includes its own configuration. Available settings include:

• Project information
• Environment Variables
• API configuration
• Runtime configuration
• Deployment settings
• Export preferences

These settings only affect the current project.

Best Practices

For the best experience, we recommend:

• Use one project per backend application.
• Split large applications into multiple workflows.
• Store secrets using Environment Variables.
• Keep development and production environments separate.
• Use descriptive names for projects and workflows.

Following these practices keeps your projects organized and easier to maintain as they grow.

Next steps

Visual Builder Overview

Learn how to design your backend visually.

Workflows

Organize backend logic into reusable workflows.

Environment Variables

Manage secrets and configuration securely.

Deployments

Publish your backend to production.

Framework Export

Export your complete backend source code.