Core instances

A Core instance is a specific Comers Core environment linked to your Organization.

This is the instance where you work day to day with orders, products, warehouse, messages, and the other Core modules.

An instance can be maintained by Comers or run as self-hosted.

Instance and Organization

A Platform Organization can be linked with Core instance context.

An instance record in Start can show information such as:

• instance name,
• deployment type,
• current status,
• linked Platform Organization,
• linked Core Organization,
• Core instance identifier,
• creation information.

This makes Start the customer-facing place for understanding which Core runtime belongs to which Platform context.

Platform Organization and Core Organization

An instance connects the two organization layers.

flowchart TD
    P[Platform Organization] --> I[Core instance]
    I --> C[Core Organization]
    C --> W[Operational Core workspace]

The Platform Organization remains the customer lifecycle container.

The Core Organization is the operational context inside that Core runtime.

Instance state

Each instance has a current status, such as active, pending, or inactive.

Core can be launched only when the instance is active and correctly linked to a Core Organization.

If the instance is disabled, waiting for configuration, or has been unlinked, it will not be available for normal work.

Launching Core

Open an instance and choose Launch Core if:

• the instance is correctly linked to a Core Organization,
• it is active,
• you have permission to launch it.

After you choose this option, Comers takes you to the appropriate Core panel.

You do not need to sign in separately to each instance every time you launch it.

Enrollment creates the relationship

Before a new self-hosted Core instance is ready for normal use, it must first be connected to an Organization in Comers Start.

A one-time token generated in Start is used for this.

After the token is used, Comers records the link between that Core instance and the selected Organization.

See Enrollment.

Generating a new enrollment token from an instance

In the instance details, you may see Generate enrollment token if you have the appropriate permissions.

The token is used to securely connect the Core instance to the selected Organization.

It is not a password or a token for day-to-day sign-in.

The token is valid only for a limited time, so treat it as confidential and use it only while configuring the instance.

Unlinking an instance

If you have the appropriate permissions, you can unlink a Core instance from the Organization.

After it is unlinked, it can no longer be launched from Comers Start as an active environment for that Organization.

The instance history itself is not deleted.

Use this option only when you really want to break the link between the Organization and that Core instance.

SaaS and self-hosted

Comers supports both Core instances maintained by Comers and self-hosted installations.

In both cases, the instance must be correctly linked to an Organization in Comers Start.

With self-hosted Core, the user usually goes through the instance connection process using a token.

With Core maintained by Comers, some of these steps can be completed automatically, so Start may offer slightly different options.

Permissions

Different actions use different Organization permissions.

For example, launching Core, managing instances, and issuing enrollment tokens are separate capabilities. Being able to view an instance does not imply permission to unlink or re-enroll it.