Each environment is automatically destroyed after 2 hours
The personal space, where you can test Artifakt free of charge, uses Cloud resources shared with all other Artifakt users.
Project codenames are unique and the namespace is shared between all Artifakt users. In other words, after a project has been created, its codename cannot be used by another personal space until the project is deleted.
Workspaces represent the highest level of organization within Artifakt. They allow you to organize your company's projects and facilitate collaboration between your teams. Simply put, a workspace contains one or more projects and each project contains one or more environments.
Typically, users create one workspace for their company or multiple workspaces if they wish to divide their company into different business units. Each workspace has its own invoicing.
Workspace codes are unique and the namespace is shared between all Artifakt users. In other words, after the creation of a workspace, its code cannot be used by another workspace until the workspace is deleted.
When you create a workspace, you have to define 2 important parameters:
The cloud provider (Amazon Web Services, Microsoft Azure, etc.) you want to use to deploy your web applications. We then create the Cloud account associated with your workspace. Please note that all workspaces are completely isolated from one another and do not share any resources.
The Cloud provider you define for your workspace is valid for all projects within your workspace and cannot be changed afterwards. We recommend that you choose it carefully.
The default deployment region. Each new project will use the default region defined in the workspace but you can always adjust the value when creating new projects. The workspace default deployment region can be changed afterwards (only the workspace owner can perform this action). Please note, such a change will only apply to new projects.
Projects help organize your company's applications and associated environments. Each project is associated with a Git repository (example: 1 project for a Magento ecommerce site, 1 other project for an Akeneo PIM, etc.). It is therefore impossible with Artifakt to deploy 2 applications in the same project and on the same architecture.
When you create a project, you have to define important parameters:
The project code (will be used for Artifakt domains)
The runtime you want to use (PHP, Node.js, Magento, Symfony, etc.)
The deployment region of your application
Project codes are unique within a workspace. After a project has been created, its code cannot be used again in the same workspace.
The runtime and the deployment region you define for your project cannot be changed afterwards. These 2 pieces of information are intimately linked to your project and modifying them would result in far too much management complexity. If you wish to use other parameters, we invite you to create another project.
Environments live within projects. Each environment corresponds to a version of your application deployed online (example: staging, preprod, dev, production, etc...).
Environments never share the same Cloud resources. They are isolated from each other and use dedicated Cloud resources. Therefore if an incident occurs on one of the environments, the others will never be impacted.
For more information on environments, we invite you to discover their life cycle.