Download

Download Emolysis.

There is nothing to download yet. Emolysis is in private development. Signed builds of the desktop app for macOS and Windows and a Linux AppImage are planned, and each one includes the emo command line and the MCP server.

Apply for early access

In private development · No release date

Availability

As of 23 Oct 2026

Desktop app

  • macOSNot available yet
  • WindowsNot available yet
  • LinuxNot available yet

Terminal and editors

  • emoNot available yet
  • emo mcpNot available yet

Desktop app

  • Platform

    macOS

    Planned

    A signed desktop build with signed updates.

    For Apple silicon and Intel Macs. The earliest macOS release is not decided yet.

  • Platform

    Windows

    Planned

    A signed desktop build with signed updates.

    For 64-bit Windows, as an installer. The earliest Windows release is not decided yet.

  • Platform

    Linux

    Planned

    A desktop build with updates, checked against its published checksum.

    For 64-bit Linux, as an AppImage. Supported distributions are not decided yet.

Every desktop build is planned to include

  • The engine and DuckDB, so there is no database to install separately.
  • The emo command line and the MCP server.
  • Signed updates on macOS and Windows and a published checksum on Linux, so you can check that an update came from us.

Command line and MCP server

  • emo

    emo command line

    In development

    Every Emolysis command from a terminal, for scripts and CI, with the same commands as the app.

    Included with the desktop app. A package on PyPI is planned.

    Planned for

    • macOS
    • Windows
    • Linux
    How it works
  • emo mcp

    MCP server

    In development

    Lets an editor or coding agent that supports MCP use Emolysis, signed in to your Emolysis account like every use of Emolysis.

    Ships with the emo command line, so it comes with every desktop build.

    Planned for

    • macOS
    • Windows
    • Linux
    How it works

Install (planned) and commands

What you run.

The commands below exist in the engine. The install is planned: no build is released, so there is no installer, package or command to run today. Dashboards from a question start from /dashboard in the app's agent.

Install

Planned
  • Desktop app

    A signed installer on macOS and Windows, and an AppImage on Linux.

  • emo command line

    Included with the desktop app. Nothing to install separately.

  • MCP server

    Included with emo. Add one configuration entry to your editor or coding agent.

No install command exists yet. Do not run one that claims to install Emolysis.

First commands

Not available yet
  • emo doctor

    Check the engine, DuckDB, DuckLake, the SQL dialects and the templates.

  • emo login

    Sign in to your Emolysis account. Every use needs one.

  • emo init orders --platform databricks

    Create a pipeline project: models, pipelines, tests and emolysis.yml.

  • emo connect databricks

    Connect a platform with its own sign-in.

  • emo mcp

    Start the MCP server over standard input and output.

MCP server: configuration entry

Not available yet
{
  "mcpServers": {
    "emolysis": { "command": "emo", "args": ["mcp"] }
  }
}

Most MCP clients take an entry like this one. The exact file and format depend on your editor or coding agent. The entry needs the emo command line, which is not available yet.

Planned system requirements

These are the requirements as designed today. Exact versions and disk space come with the first release.

Operating system
A recent, supported release of macOS, Windows or Linux. Exact versions come with the first release.
Disk space
Room for the app and for the samples you pull into DuckDB. Samples are small slices of your tables, not full copies.
Network
Needed to write code, to connect and deploy to your platform, and to publish dashboards. Templates and golden tests on local files run on your machine.
Model access
A key from the model provider you choose, on any plan, or a paid plan's model usage.
Platform account
An account on your data platform with rights to read its catalog and create its deployment units. We recommend a development workspace.
Credential store
Your operating system's keychain, where platform credentials and model keys are kept.

Until then

What exists today, and what to ignore.

  • A placeholder package name

    The name emolysis is reserved on PyPI with an empty placeholder. Installing it gives you nothing usable. Do not install it.

  • Anything that claims to be Emolysis

    Do not trust a download, package or installer that claims to be Emolysis until we announce a release on the news page. If it exists before then, it did not come from us.

  • The template format

    The template format and its validator are public on GitHub (emolysis/template-sdk). You can read the format today. The package is not published.

  • Editor and coding agent setup

    The setup configs for editors and coding agents are public on GitHub (emolysis/integrations). They need the engine, which is not released.

How you check a build (planned)

When builds are released, this page lists the following, so you can tell a real build from a copy.

  • The signing identity for macOS and Windows.
  • The checksum file published with each release.
  • How to verify both. A build that does not verify did not come from us.

News page · Optional newsletter

Hear about releases.

We announce releases on the news page. To try Emolysis before a public release, ask for early access. The request form also has an optional newsletter, at most once a month.