Frequently asked questions about Melta

Complete digital products from a plain-language description: web apps, SaaS products, portals and shops. That includes the interface, the logic, user accounts, its own isolated database, payments, email, legal pages, a support inbox, cookieless analytics and error monitoring. Melta does not just build the product; it puts it online and operates it.

No native apps for the app stores; a Melta product runs in the browser, on phones too. No video hosting and no storage for large files: you embed videos from your video host. And no automatic splitting of payments to third-party sellers, for example on a marketplace; there you earn through listing fees, vendor subscriptions, featured placements or booking fees that you collect yourself.

In your own words, as you would explain it to a friend: who it is for, what someone does with it, what is free and what people pay for. You do not need technical terms. If something important is missing, Melta asks up to four non-technical questions, about the audience or the payment model for instance, before the concept is written.

From your description Melta writes a concept in plain language: which pages exist, what users can do, how payment works. You read it and change it in the chat until it fits. The concept costs nothing and commits you to nothing. Only when you click Build are credits used.

Melta builds the entire product, typically within 24 hours. You get an email when it is done. If a build fails, nothing goes online, you get an email as well, and the build is picked up again. The build is booked once per product, not per attempt; a failed run costs no credits.

The build has a fixed one-time price per product, due when you confirm the concept. It includes the complete first build, from the interface through to payments and legal pages. The amount is on the pricing page.

Four plans per organisation: Starter, Growth, Scale and Enterprise. They differ in the number of products, team size, custom domain and the share of your sales. Hosting, payments, email, domain, legal pages, support inbox, monitoring and analytics are part of every plan, as are change runs and an AI quota. Prices and details are on the pricing page.

Your plan's share applies only when your product sells something; card processing comes on top. Both are deducted from each payment and never invoiced separately. If you sell nothing, you pay only the plan. The rates per plan are on the pricing page.

Paying annually is cheaper than paying monthly; by how much is on the pricing page. The scope of the plan stays the same, and you decide per organisation whether to pay monthly or annually.

The product is yours: the concept, the content, your users' data, the design, the revenue and the source code. You export the code to a GitHub repository of your own at any time with one click, images included, and you can read it in the Code tab of your product. To be honest, the product is built for Melta: hosting, payments, email, domain, legal pages, support inbox, monitoring and analytics are platform services that need replacing if you run it elsewhere. No lock-in on the code; the operation is the part Melta takes care of.

Every build lands first in a private preview only you can see, seeded with demo data and named test logins; test purchases use test data and no real money. Going live takes seconds, with no rebuild; before that Melta checks that your operator details are complete and, if your product sells something, that the payout account is connected. On go-live you choose which preview data to carry over. Rolling back to the previous live version is possible.

Every product starts on a melta.ai subdomain. From the Growth plan you use your own domain: buy it through Melta or connect one you already have. Your product's emails then go out under your domain as well.

Yes. Confirmations, password links and receipts go out under your product's name, from no-reply@yourproduct.melta.ai or your own domain, with attachments such as PDF receipts when needed. Replies land in your product's support inbox at support@yourproduct.melta.ai. Incoming mail is categorised automatically and you answer from within Melta. An AI auto-reply is available, off by default, and hands over to you.

Yes. Imprint, privacy policy and terms are generated from your operator details and can be edited without a rebuild. They are aimed at Switzerland, Germany and Austria. This is general information, not legal advice; when in doubt, have them reviewed.

Not for Melta's analytics. They measure without cookies and without third parties: visitors, pages, sources, countries, devices, campaigns, the funnel from visit through signup and checkout to purchase, revenue per source, a live view and page speed. A report arrives by email once a week.

In a chat with your product's editor: “make the button green”, “add a waitlist”, “change the price”. You watch the editor work, can steer or interrupt mid-run, and the preview updates live. From the chat you deploy the change to preview or live. Change runs are included in every plan.

In the language of your idea: describe your product in English and the interface, emails and forms are English throughout; describe it in German and they are German. The Melta interface itself exists in English and German.

Melta is built and run from Grabs in the St. Gallen Rhine Valley in Switzerland, founded by Stefan Laggner, and is aimed first at Switzerland, Germany and Austria; the legal pages are designed for those countries. Melta is in early access: you join the waitlist and receive an invitation when it is your turn. Questions, partnerships and press: hello@melta.ai.