Managing applications composed of multiple microservices often requires creating separate projects for each service, such as backend, frontend, and infrastructure.

This approach leads to fragmented management, making it difficult to maintain a unified view of your infrastructure, costs, and deployments. This complexity is further increased when trying to scale or add new services to existing projects.

To address these challenges, we’re excited to introduce Components - a new way to organize and manage your applications more efficiently.

With Components, you can now decouple stacks from projects, allowing a single project to contain multiple, distinct components, each linked to a specific environment and stack.

For example, instead of managing separate projects for different parts of your application, you can now create a single project named Cycloid that includes:

• Cycloid Backend for your API and business logic.

• Cycloid Database for deploying the database that will be used by the Backend

• Cycloid Frontend for the user-facing interface.

With this new architecture you now have a centralized and cohesive view of your entire application, which streamlines workflows by reducing the need to switch between projects.

Thanks to Components you can easily create and scale granular environments, adding new services as needed - without having to refactor or duplicate existing ones.

Components also simplifies management and enhances visibility into resource usage, costs, and deployments across all elements of your application. This means you can focus resources on building and deploying your services instead of managing complex project structures.

A project section completely reimagined

With the components layer, it was necessary to redesign the whole project and environment creation.

Based on customers feedback and discovery calls, we worked on a better user experience to see at a glance, all the information that really matter to users.

The project view is now listing all the environments available with the components that belong to those environments.

We are introducing the component view, with the pipeline directly available on the overview, but also the quick switch to jump into a sibiling component:

We are really excited to see how you will use this awesome feature and how you will evolve your stack around this new granularity !

Don't hesitate to give some feedback through our roadmap section.

How to use the new components ?

With the components layer, we upgraded our stack format to handle this new entity.

Cycloid is still compatible with your current stacks on V3.

In order to use the full potential of components and have multiple components per environment, you will have to migrate your stacks to the V4 format.

For the migration process, we prepared a how-to that you will find in our cookbook.

To get more information about the components concept, check our dedicated documentation on components.

Changelog v6.0.17

• ADDED

  • Components: Adding the component layer

  • InfraView: Improved empty state message for missing TFState files

  • General: Add tracing using Sentry for Backend and Frontend

• FIXED

  • Infraview: Uncaught error while hovering or clicking certain resources

  • Logs: Broken date picker for logs time range

  • Stackforms: Fixed a panic that could occur when TF form variables had invalid module keys

  • API: Fixed error responses returned on OpenAPI errors

  • Environments: Fixed wrong validation being applied for environment canonical when length was less than 3 characters

  • Members: Ensure names with ' and ` are also valid