Melta
Who it is for
Melta for people with an idea and no coding skills
For anyone who knows exactly what their product should do but cannot write a line of code. You describe it in your own words. Melta turns it into a complete product with logins, a database, payments and legal pages, puts it online and runs it. Later you change it by chat.
Where you are today
The idea has been with you for a while, maybe years: a booking tool for your studio, a tool for your trade, a member area for your guides. Site builders often run out of road at logins, subscriptions or payouts, and agencies quote amounts and timelines that do not fit a first version. This is where Melta comes in: you bring the idea, Melta builds and runs the product. You never need to know what a database is or how to manage a server.
What you bring and what you do not need
What you bring
Your idea in your own words. Your operator details (name, address, contact) for the imprint, privacy policy and terms. A bank account if your product sells something. Some time to test the preview.
What you do not need
No coding skills, no developer, no designer. No hosting account, no server, no separate contract with a payment provider. No specification document: if something is unclear, Melta asks up to four questions in everyday language.
What Melta builds for you
Bookings for what you offer
Classes, appointments, seats: your customers book and pay online and you see who is coming, like the example product SOMA Yoga Zürich.
A tool for your trade
The routine you run on paper and spreadsheets today, as an application with accounts and records, like AbnahmeBlitz for construction acceptance or FristenWächter for inspection deadlines.
Knowledge you sell
Guides, templates or a step-by-step manual behind a login, sold once or as a subscription. KettenDoc for bike repairs shows what such a guide can look like.
A guide with sponsors
A directory or route guide for your niche, funded through sponsor packages, like Steigwärts for via ferratas.
Each comes with logins, its own database, payments, email under its own name, a support inbox, legal pages, a design system, analytics and error monitoring. More product types are listed under Solutions.
What a good description looks like
No technical terms, just clear sentences about four things: Who uses the product? What does that person do in it, step by step? What costs money, paid once or regularly? What do you want to see and do yourself? For example: "I teach sewing classes. Participants should see the classes, book a seat and pay online. I want to see who is signed up and send a reminder for the next date after each class." That is enough to start; Melta asks about whatever is missing.
Step by step
- Describe - You write your idea in everyday language, in English or German; your product is built in that language.
- Read the concept - Melta writes a concept in plain language: pages, flows, roles, payment model. You change it by chat until it fits. Up to here you pay nothing.
- Have it built - When you approve, the build starts, paid from the credits of your plan. Melta builds interface, logic, accounts, database, payments, email and legal pages, typically within 24 hours, and emails you when it is done.
- Test the preview - Your product sits in a private preview, seeded with demo data and named test logins. You click through it, buy with test data and try every flow. No real money moves.
- Go live - First Melta checks that your operator details are complete and, if you sell, that your payout account is connected. Going live takes seconds, with no rebuild. You choose which preview data comes along, and you can roll back to the previous version.
- Change by chat - "Make the button green", "add a waitlist": you write it to your product's editor, watch it work, step in when you want to, and deploy the change to preview or live. Change runs are included in every plan.
What happens after go-live
Your product runs on globally distributed hosting, isolated with its own database, and scales by itself. Messages from your customers land in the support inbox, sorted automatically, and you answer from Melta. Cookieless analytics show where visits and revenue come from, with a weekly summary by email. Errors from browser and backend appear in one feed. There is no maintenance contract, because running the product is part of the plan.
What it costs
A concept uses only a few credits; afterwards your product runs on a plan per organisation with credits every month. All numbers and how the price is made up are on the pricing page.
Common questions
Do I really not need to know anything technical?
No. You describe what your product should do, read the concept in plain language and test the preview the way a customer would. Melta asks its questions in everyday words, at most four. Hosting, database, payments and email are set up and run by Melta for you.
What if my description has gaps?
That is normal. Melta asks up to four non-technical questions and then writes the concept. It shows you how your idea was understood, and you change it by chat until it fits. Nothing is built until you approve the concept.
What happens if something breaks after launch?
You write it in the chat. Your product's editor reads the error logs itself, fixes the cause, and you see the change in the preview first. If a go-live goes wrong, you can roll back to the previous live version.
Can I keep developing my product later without a new build?
Yes. New features, different prices or an extra page are chat messages to the editor. Colours, fonts and legal pages change on their own pages, without a rebuild. The build is paid once per product.
Your idea in your words. Melta does the rest.
The concept costs only a few credits and needs no technical terms. Once you approve it, Melta builds your product, puts it online and runs it.
Get early access