Support
Get help.
Emolysis is not released yet, so there is no product to support. Questions and feedback are welcome. This page says how to reach us, what to include and what to expect.
Channels
Read the docs
How Emolysis works: projects, pipeline shapes, templates, golden tests, dashboards and the error codes every surface returns.
Open the docsBrowse the FAQ
Short answers about platforms, what leaves your machine, plans and keys, dashboards and where things stand.
Read the FAQEmail us
The one channel that reaches the team. Write in English or German. The message opens prefilled with what we need.
Write to usGitHub
The public repositories hold the template format and the setup for editors and coding agents. Open an issue there for problems with them.
Open GitHub
The address is hello@emolysis.com. If your email app does not open, copy it and add the details below.
Follow Emolysis
- GitHub: github.com/emolysis
- LinkedIn: linkedin.com/company/emolysisai
- Instagram: @emolysis_en
- Facebook: Emolysis
- Crunchbase: crunchbase.com/organization/emolysis
What to include
What to include.
A good request lets us understand the problem without a second round of questions. The email link above opens with these prompts filled in.
Include
- What you were trying to do, and what you expected.
- What happened instead, in your own words.
- Which surface: the desktop app, the emo command line, the MCP server or this website.
- Your operating system, and the Emolysis version once there is one. For a problem with this website, the page and your browser.
- The error code and message, if there is one. Every surface returns one of nine error codes.
- The data platform and the pipeline shape, if they matter.
- The steps to reproduce it, and the output of emo doctor once you have a build.
Leave out
- Credentials, tokens, keys, passwords or connection strings.
- Real customer data, or query results and samples with real values. Describe the table, or use made-up values.
- Material you are not allowed to share under a confidentiality agreement.
- A security vulnerability in a public issue. Report it privately instead.
What to expect
What to expect.
There is no product to support yet
Nothing is released, so there is no release to run into problems with. We do want to hear what is unclear on this site, what you would need to try Emolysis and what would stop you.We reply by email
We answer by email, in English or German, in the order messages arrive. We do not promise a response time, and there is no support plan or service level yet.Security reports are a priority
We treat vulnerability reports as a priority. Send them to us privately, never in a public issue, and give us a chance to fix the problem before you publish details.