Docs

Installation (planned)

What Emolysis installs as, on which systems, and what exists today. No build is released; the emolysis package name is only a placeholder.

Planned

Updated Oct 23, 2026

Docs menu · 25 pagesInstallation (planned)

Status

Planned. Not yet available, and the details on this page can change before the first release.

On this page

There is nothing to install yet: no build, package or installer is released. This page describes what Emolysis installs as, and what to ignore until a release is announced.

What Emolysis installs as

  • The desktop app for macOS, Windows and Linux. It includes everything you need: the engine, DuckDB, the emo command line and the MCP server. Release builds for macOS and Windows are signed; on Linux the app is an unsigned AppImage, checked against its published checksum. The app updates itself, with signed updates on macOS and Windows. No build is signed or released yet.
  • The emo command line, for terminals, scripts and CI, with the same commands as the app. A package on PyPI is planned. See The emo CLI.
  • The MCP server, emo mcp, which ships with the command line and lets an editor or coding agent that supports MCP use Emolysis. See The MCP server.

The three are one engine with three front ends, so you never install a different product for each.

What you need

  • An operating system. A recent version of macOS, Windows or Linux, with enough free disk space for the samples you pull into DuckDB. Samples are small slices of your tables, not full copies. Exact system requirements are published with the first build.
  • An Emolysis account. Every use of Emolysis needs one, local files included, and the Free plan is one.
  • A way to reach a model. To write code, you need either your own key from the model provider you choose, on any plan, or a paid plan's model usage. See Model keys and credits.
  • For a platform: an account on that platform with rights to read its catalog and create its deployment units. See Connecting Databricks.
  • For pull request checks: a CI system that can run emo check. A reusable GitHub Actions workflow, in preview, runs emo check in your own CI; it needs the emo command line, which is not released yet. The GitHub App is planned. See GitHub checks.

What exists today, and what to ignore

  • The name emolysis is reserved on PyPI with an empty placeholder. Installing it gives you nothing usable. Do not install it, and do not trust any package or download that claims to be Emolysis before we announce a release on the news page.
  • The template format and its validator are public on GitHub, in emolysis/template-sdk. You can read the format today; the package is not published. See Templates and slots.
  • The setup configs for editors and coding agents are public on GitHub, in emolysis/integrations. They need the engine, which is not released.
  • This website has a sample dashboard on synthetic data. It shows what the agent's charts look like; it is not the product.

How to check a build

With each release, this page lists the signing identity for macOS and Windows and the checksum file published with the release, and how to verify both. A build that does not verify did not come from us.

After installing

Run emo doctor to check the setup: the engine version, DuckDB, the credential store, and whether a model key or plan is configured. Each failed check says what to fix, and emo doctor exits with an error when a required check fails, so scripts and CI can rely on it. See Troubleshooting.

Updates and removal

Release builds of the desktop app update themselves, with signed updates on macOS and Windows; none is released yet. Your projects are plain folders in your own repositories, so they do not depend on the app being installed. How removal works is published with the first build.