Skip to content
Craftifact

Start a demo instance

Concise guide to the approved demo flow from request to a running temporary instance.

Before you start

This page covers the provisioned demo flow in the Control Plane. It is different from the public read-only product demo on the website.

Quick path

  1. Request the demo subscription through the shop flow.
  2. Wait for manual approval. After approval, the email links you back to the Control Plane.
  3. Start the demo from the Control Plane within the approval window.
  4. Create the instance just like a paid instance.
  5. Provisioning success starts the demo runtime window automatically.

Demo rules that matter

  • Manual approval is always required before you can start.
  • You must start the approved demo within 7 days.
  • Each approved demo session can start one instance.
  • The runtime lasts 8 hours from successful provisioning.
  • A reminder email is sent shortly before cleanup.
  • Backup and restore are disabled for demo subscriptions.
  • Repository import stays available in demo mode.
  • There is no in-place demo-to-paid conversion. Paid usage starts with a fresh instance.
Rationale: why the demo still starts in the Control Plane
The demo uses the same control-plane entry point as paid instances so you can evaluate the real provisioning and management workflow instead of a separate simplified UI.

Identity and account separation

The demo instance login is still separate from the shop account that requested the demo. With the managed SoluForge IdP, the initial admin account is created in a dedicated instance realm, not in the shop realm.

What happens after the demo ends

  • The demo instance and its demo subscription are cleaned up automatically.
  • Managed IdP user accounts are not deleted automatically. If you need cleanup there as well, contact support.
Rationale: why there is no demo-to-paid conversion
Current behavior keeps the demo lifecycle simple and predictable. If you decide to buy later, plan for a fresh paid instance instead of expecting an in-place upgrade path.

Where to go next