Skip to main content

Projects

A project is the main unit of work in Fransys. It groups all the blocks (applications, databases, services) that make up your infrastructure and deploys on a cluster.

Each project has its own visual canvas where you assemble your infrastructure using drag-and-drop.

Create a project​

From the Projects page of the dashboard, click Create project.

The project is created immediately with a default name. No form to fill out — you are directly redirected to the project's canvas, ready to add your blocks.

tip

Rename your project right after creation to easily find it if you manage several projects.

Project view​

Once inside a project, the interface consists of two areas:

  • Left sidebar — The list of available blocks, organized by category:
    • Application: Laravel, React, Angular, Vue.js, Docker
    • Database: MariaDB, PostgreSQL, Redis
    • Socket: Soketi
    • Standalone: Custom blocks
  • Canvas — The workspace where you drag and drop your blocks to build your infrastructure

In the top right, the Select cluster button lets you associate a cluster with your project before deployment.

Rename a project​

The project name is displayed in the top left of the canvas. Click directly on it to edit — the field becomes editable. Confirm to save the new name.

Project statuses​

A project can have two statuses:

  • Online — The project is deployed and active on its cluster. The blocks are running in production.
  • Offline — The project is stopped. The configuration is preserved, but no resources are consumed on the cluster.

Switching a project to offline lets you keep your entire configuration without consuming credits — useful for test environments or projects temporarily paused.

Delete a project​

From the Projects page (list of all your projects), a dropdown menu is available on each project. Click it and select Delete to remove the project.

caution

Deleting a project is permanent. All blocks and their configuration are deleted. If the project is online, the resources deployed on the cluster are also released.

Best practices​

  • One project per application or environment — Separate your projects by logical scope (e.g., one project for production, another for staging when environments become available).
  • Name your projects clearly — Use an explicit name from the start, especially if you manage multiple projects in parallel.
  • Switch to offline rather than delete — If you no longer need a project temporarily, switch it to offline to keep the configuration at no cost.