Melta
Features
Maintenance: included in every Melta product
For anyone who wants to keep developing their product after the build without hunting for developers or writing tickets. At Melta you work with your product in a chat: you describe in your own words what should be different, the editor reads the real code and changes it, and you watch it work. The preview follows live, and when it is right you put the change live with a button.
What you get
A finished product is never finished: a button should turn green, a waitlist should be added, a text should read differently, a price should change. At Melta that is not a request to an agency but a message to your product. The editor knows the code the AI agents built and works directly in it.
Changes in plain words
You write what you want: “make the button green”, “add a waitlist”, “call the page Classes instead of Offers”. The editor reads your product's real code, searches the web when a task needs it, and edits the files.
Watch and steer
A live status shows what the editor is doing right now: reading, searching, editing. If something occurs to you along the way, you add it. If it heads in the wrong direction, you interrupt the run.
Questions and data
The chat answers questions about your product, including about the data: “How many courses are there?” On request it creates, changes or deletes records in the preview database.
Preview and go-live from the chat
While the editor works, the preview updates live. “Deploy to preview” and “Go live” are buttons, and the chat shows you the deploy status.
A change takes minutes, not seconds: the editor reads, edits and checks. The conversation history is kept, so you can pick up an earlier change where you left it.
How it works
- Describe - You open your product's chat and write what should be different, in full sentences and without technical terms. The more concrete, the better: which page, which element, which behaviour.
- Watch - The editor reads the files involved, searches the web if it needs to and edits the code. You see every step with a live status. You can add instructions or interrupt the run at any time.
- Check in the preview - The preview updates while the editor works. You click through, test with the demo data and test logins and say what is still missing. The chat remembers the whole conversation.
- Let it be checked - Before a deploy your product is checked automatically: type check, build and the layout at 390 pixels wide. If the checks find something, the editor fixes it before the change moves on.
- Deploy or go live - “Deploy to preview” and “Go live” are buttons in the chat. The deploy status appears in the conversation, and when the change is live you see it there.
What runs in the preview and what runs live, how going live works and how you roll back to the previous version is on the page Preview and live. If monitoring reports an error, you describe it in the chat; the editor reads your product's logs for that.
Who this matters for
A product lives on being changeable once the first people use it. Three cases where the chat makes the difference:
- Founders with a SaaS product - Whoever runs a SaaS product with subscriptions learns something every week: a feature is missing, a tier is cut wrong, a price no longer fits. Each of those changes is a message, and it goes to the preview first.
- Studios with a booking system - A studio with a booking system asks the chat how many classes are set up, has a class created in the preview and checks whether the class page still fits. The example product SOMA Yoga Zürich shows what such a product looks like.
- Anyone who does not code - If you do not program, you never need to read code. You describe what you see and what you want; what the editor does appears as a status in the chat, and the result appears in the preview.
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 need to know how to code to change something?
No. You describe the change in your own words, for example that a button should turn green or a waitlist should be added. The editor reads your product's code and changes it. You see in the chat what it is doing, and the result in the preview.
How long does a change take?
Minutes. The editor reads the files involved, searches the web if needed, edits the code and has the product checked. You do not wait in the dark: the status shows every step, and the preview updates while it works.
Does a change go live straight away?
No. It lands in the preview first. Going live is a separate button, and before that your product is checked automatically: type check, build and the layout at 390 pixels wide. Whatever the checks find, the editor fixes.
Can the chat work with my data too?
Yes, in the preview. It answers questions about the data, for example how many courses are set up, and on request it creates, changes or deletes records in the preview database.
What does a change cost?
Nothing extra. Change runs are included in every plan, from Starter to Enterprise. Colours, fonts, corner radius and shadows you can also change on the design page, without any rebuild.
Describe your product. Change it later by chat.
A concept uses only a few credits. After the build every change is a message to your product, with preview, checks and go-live from the chat.
Get early access