FAQ

Frequently asked questions.

Straight answers about what Emolysis does, what leaves your machine, what it costs and where it stands. The answers on availability give the current status.

Topics

Product

Product

  1. What is Emolysis?

    Emolysis is the agentic lakehouse for data engineering and analytics, made by Bandpey GmbH in Munich, that puts a team of agents at your direction.

  2. Who is Emolysis for?

    Emolysis is for people who own production data pipelines on Databricks, Snowflake or Microsoft Fabric, and for analysts who want a dashboard from a question.

  3. How is Emolysis different from a general coding agent?

    A general agent writes whatever a prompt suggests; Emolysis starts from a platform profile, tested templates and golden tests on your machine.

  4. What does local-first mean for Emolysis?

    Development runs on your machine with DuckDB and production runs on your platform, but that does not mean that nothing leaves your machine.

  5. Does Emolysis replace my data platform or catalog?

    No, Emolysis sits on top of the platform you already run and deploys your platform's native unit, which your team can review and operate.

  6. Which AI model does Emolysis use?

    Emolysis works with your own key from the model provider you choose, on any plan, or with a paid plan's included model usage instead of a key.

  7. Can I use Emolysis from my editor or coding agent?

    Yes, the MCP server, emo mcp, lets any editor or coding agent that supports MCP use the same commands as the desktop app, with one config entry.

  8. Does Emolysis deploy anything without my approval?

    No, deploying is a step you take yourself, and only after lint, a DuckDB dry run and the golden tests on your machine have all come back green.

Platforms

Platforms

  1. Which platforms does Emolysis support?

    Databricks is first, Snowflake and Microsoft Fabric are planned, PostgreSQL is in development as a source, SQL Server is planned as one.

  2. Why is Databricks first?

    Databricks has the complete set of APIs Emolysis needs to prove the whole loop, from a question to a tested, deployed pipeline and a shared dashboard.

  3. Is there a date for Snowflake and Microsoft Fabric?

    There are no dates yet: both are planned after Databricks, and the news page announces each one when its templates pass their tests there.

  4. What is a platform profile?

    A platform profile describes a data platform for the agent, which loads it when you connect a workspace and writes code the way that platform expects.

  5. Can I move a pipeline from one platform to another?

    Yes, as an explicit step in which the pipeline is translated to the target platform's dialect and its golden tests run again.

  6. Can Emolysis read from SQL Server or PostgreSQL?

    PostgreSQL is in development as a source and SQL Server is planned: Emolysis reads from them, lands the data on your platform and never deploys to them.

Pipeline shapes

Pipeline shapes

  1. What are pipeline shapes?

    A pipeline shape is a recurring kind of data pipeline with a known correct form, and about ten shapes cover most production work.

  2. Which ten shapes does Emolysis cover?

    Ingest (batch), Incremental append, CDC merge, SCD Type 2, Snapshot, Backfill, Late-arriving, Dedupe / conform, Aggregation / gold and Reverse ETL.

  3. What if my pipeline does not fit one of the ten shapes?

    Most real pipelines are several shapes in a row, and when a request fits none the agent says so instead of improvising code it cannot test.

  4. What is a golden test?

    A golden test runs a pipeline on a fixed input and compares its output with an expected output row for row; a failure sends the agent back to the template.

  5. Why test on DuckDB instead of on my platform?

    DuckDB runs on your machine with no cluster, so a golden test takes seconds and spends no warehouse compute, which makes testing on every save practical.

  6. Can I write my own templates?

    Yes, the template format is public under the MIT license, and you can write templates for your own recurring patterns and use them in your projects.

Security and data

Security and data

  1. Does my data leave my machine?

    Some of it can: prompts go to the model provider you choose and can include schemas and sample values, and a dashboard leaves only when you publish it.

  2. What does the AI model provider see?

    It sees the agent's prompts and the responses it returns, which can include table and column names, schemas, templates and sample values from your data.

  3. Where are my platform credentials stored?

    They are kept in your operating system's credential store and not sent to Emolysis, whose services never connect to your data platform.

  4. Does Emolysis store my data on its servers?

    Only what you publish, because Emolysis's services hold your account, plan and usage records, and the dashboards you choose to publish.

  5. Can I limit what the agent sends in prompts?

    No dedicated setting yet: you limit what the agent sees with a development workspace, non-sensitive tables and synthetic test fixtures.

  6. What permissions does Emolysis need on my platform?

    Emolysis acts with the permissions of the account you sign in with, no more, so a role limited to a development workspace limits what it can do.

  7. Is Emolysis certified for SOC 2 or similar standards?

    No, Emolysis is in private development and has not been through a third-party audit, penetration test or compliance certification.

Pricing and plans

Pricing and plans

  1. Is Emolysis free?

    There is a Free plan at $0, and because it is bring your own key, you pay your model provider directly and Emolysis charges nothing for it.

  2. What does bring your own key mean?

    You add a key from the model provider you choose, the agent uses it, that provider bills you directly, and Emolysis adds nothing to that bill.

  3. Can I use my own key on a paid plan?

    Yes, every plan accepts your own model key, and requests made with it are billed by your provider and do not count against your plan's limits.

  4. What do the paid plans add?

    Pro adds every platform connection, sharing and GitHub checks, Max more included usage, Team shared workspaces, and Enterprise controls and support.

  5. How is Max different from Pro?

    Max is for people who build with the agent all day, and it adds 5x or 20x Pro's included usage, priority access at busy times and early access.

  6. How do Team seats work?

    Team is for 2 to 150 people, with standard seats at $25 and premium seats at $125 per seat a month, and lower prices when billed annually.

  7. How does Enterprise pricing work?

    Enterprise is US$20 per seat a month billed annually, plus model usage at metered rates, with a 20-seat minimum for self-serve, at planned prices.

  8. Can I pay annually, and does it cost less?

    Yes for Pro and Team, where annual billing costs less per month, while Max is billed monthly only and Enterprise annually only, at planned prices.

  9. How do usage credits work?

    Usage credits on Pro, Max and Team keep the agent working at standard metered rates after you reach your plan's included model usage.

  10. How do usage limits work, and what if I reach one?

    Included usage is measured by the work the agent does, and at a limit you can wait, use your own key, change plan or turn on usage credits.

  11. Does Emolysis charge for my warehouse compute?

    No, deploys and production runs use your platform's compute and appear on your platform's bill, and local iteration uses no cluster hours.

  12. Can I buy a plan today?

    No, Emolysis is in private development, nothing is for sale, and the prices on this site are planned prices that may change before release.

Dashboards and sharing

Dashboards and sharing

  1. How do dashboards from a question work?

    You type a business question, and Emolysis builds a tested gold table behind it and picks charts for you to review before you publish a link.

  2. Who can see a dashboard I share?

    You choose when you publish from three settings, anyone with the link, members of your organization or only you, with organization as the default.

  3. Can I change who can open a shared dashboard?

    Not on its current link: revoke the link, then publish the dashboard again with the setting you want, which makes a new link with a new URL.

  4. Can I update a shared dashboard?

    Yes, a dashboard keeps one stable link and each publish adds a revision under it, so the link you sent stays the same and shows the latest numbers.

  5. What chart types do dashboards support?

    The chart spec defines seven types, bar, line, area, scatter, pie, KPI and table, and every chart also lists its data in a table.

GitHub

GitHub

  1. How does Emolysis work with GitHub?

    Your pipelines live in your own repository, and checks on each pull request, from emo check in your CI or the planned GitHub App, are the gate for every deploy.

  2. What does the GitHub App check?

    The GitHub App is planned; it checks four things on every pull request: lint, golden tests on DuckDB, a cost estimate and a preview dashboard link.

  3. Can I run the checks in my own CI?

    Yes, 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.

  4. What does an Emolysis project look like?

    A plain folder you own and keep in your own repository, with models, pipelines, tests and an emolysis.yml file that names the platform.

Company

Company

  1. Who makes Emolysis?

    Emolysis is made by Bandpey GmbH, a company in Munich, Germany, led by CEO Roozbeh Bandpey, and it is in private development.

  2. Is Emolysis open source?

    The core is closed source, while the template format and the setup configs for editors and coding agents are public under the MIT license.

  3. How can I contact the team?

    Email hello@emolysis.com, which is the one channel for general questions, early access, press and security reports while Emolysis is in private development.

  4. Does this website use cookies or analytics?

    Yes, once you choose in the cookie banner; before that it sets no cookies and keeps nothing in your browser but your theme.

Roadmap and availability

Roadmap and availability

  1. Is there a release date for Emolysis?

    There is no release date yet, because Emolysis is in private development, and the news page announces availability when there is one.

  2. Can I join early access?

    Early access is by invitation, starting with data engineering teams on Databricks, and you ask for it with the request form or by email to the team.

  3. Which operating systems does the desktop app support?

    The desktop app is for macOS, Windows and Linux, with no build released yet, and the emo command line and MCP server cover the same three systems.

  4. Does Emolysis work offline?

    Partly: golden tests on DuckDB with local files work offline, while writing code, deploying and sharing a dashboard all need a network connection.

  5. How do I hear about releases?

    On the news page and its RSS feed, which is where we announce each release, each new platform and any change to the plans and their prices.

Contact

Still have a question?

The docs describe how Emolysis works. For anything else, email the team at hello@emolysis.com.

Read the docsEmail the team