SimStudio Migrations

SimStudio Migrations is a one-time container that runs database migrations to initialize and update the PostgreSQL schema for SimStudio's self-hosted AI agent…

  • AI
  • Automation
  • Development
  • Tools & Utilities
SimStudio Migrations is a one-time container that runs database migrations to initialize and update the PostgreSQL schema for SimStudio's self-hosted AI agent and workflow platform. It must complete successfully before starting the simstudio-app and simstudio-realtime containers.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

84/100 Excellent

Maintained
100last commit 18 days ago
Popular
9029,979 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 18 days ago

GitHub stars
29,979
Open issues
352
Last commit
2026-11-03
Latest release
v0.9.41
License
Apache-2.0
Activity
declining

Checked 19 days ago - source: GitHub (simstudioai/sim)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • First install: run before the app containers Run this container once and wait for it to exit successfully before starting simstudio-app and simstudio-realtime. The wider stack is self-hosted via npx sim-setup; the macOS desktop app (macOS 12+, Apple Silicon or Intel) can be pointed at that deployment. source

Fetched 18 days ago - each note links to its source

Alternatives (3)

  • Zapier - Automate workflows effortlessly, connecting over 7,000 apps without coding.
  • langflow - Langflow is an open-source platform for building and deploying AI-powered agents and workflows.
  • n8n - n8n is a self-hosted, fair-code workflow automation platform that connects 1,500+ apps and application programming interfaces (APIs) on a v…

Checked 54 days ago - source: AlternativeTo

Common questions

Does the migrations container need to keep running after it has run the schema migrations?

No. It runs the migrations and exits, while the app and realtime services wait until the database is healthy and migrations are complete.

Which image tag should I use for the migrations container during an upgrade?

Use the same tag for the app, realtime, and migrations images because they share the database schema. Mismatched tags can make the app run against an incompatible schema.

Does npx sim-setup clone the Sim repository during self-hosted setup?

No. It creates a sim deployment directory, provisions the database, generates secrets, writes the env file, and starts the published images with Docker Compose.

Will sim-setup down delete my database or other managed data?

No. sim-setup down removes containers but keeps data. sim-setup reset archives the env file and wipes managed data.

Which local port is the self-hosted Sim app exposed on after setup?

After the setup wizard finishes, open the app on port 3000.

Answers sourced from docs.sim.ai, github.com, zread.ai

Community

Collected 49 days ago - public community threads