Skip to main content

Introduction

Mystic AI is sunsetting their services. They were an early pioneer that pushed the industry forward. This guide covers migrating apps from Mystic to Cerebrium to keep them functional. It covers converting existing Mystic code (using a stable diffusion example) and configuration to the Cerebrium platform, including deployment optimization for performance and cost efficiency.

Key Differences

Cerebrium helps teams deploy and run models efficiently. The infrastructure is designed for reliable performance:
  • The average model cold-starts in 2-5 seconds.
  • Updates to your code deploy quickly, taking only 8-14 seconds.
  • 99.9% uptime.
Cerebrium provides precise control over computing resources. Instead of managing entire instances, select the exact CPU, memory, and GPU power needed. Billing is per-second for actual resource usage. Use the pricing calculator for cost estimates.

Migration Process

1. Project Setup and Configuration

Install Cerebrium’s command-line tool and create the project:
Convert the existing Mystic configuration to Cerebrium’s format. A typical Mystic configuration:
Becomes this Cerebrium TOML config:

2. Code Migration

Convert the model implementation. A typical Mystic pipeline:
The Cerebrium equivalent in main.py:

3. Deployment

Deploy your model with a single command:

4. Inference

Once your app is deployed, you can make requests to your model using the example cURL request below:
The Cerebrium platform provides the tools and support needed for a smooth transition.

Join the Community

Connect with other developers and the Cerebrium team for faster response and issue resolution:
  • Join the Discord server.
  • Join the Slack workspace.
These communities offer migration support, quick technical answers, best practices, and feature updates.