Mail Coding
Build your app or website by email. Describe it, the first version lands in your inbox, reply to change it.
Three steps of mail coding
Describe, sign up, reply. Everything else happens in your inbox.
Write what should be built or migrated, in the box above or in an email to ai@openkbs.com. Plain language, no spec.
Your description becomes the first task and the AI Studio starts on it right away. You can close the tab.
The first version arrives with a link and a test login. Reply to the email to change anything; every answer comes back by email.
A real exchange, three emails long
The site is built after the first one. The rest is you asking for changes.
I have a WordPress site for a small furniture shop. Move it to you with a product catalogue and an inquiry form. Keep the colours.
Your furniture shop is online: https://dd2kqag.cloudfront.net — catalogue with 42 products, inquiry form that emails you, same green and oak palette. Test login for the admin: admin / temp-7f3k (temporary). What next? 1. Connect your domain 2. Add a ‘sale’ badge 3. Something else — just reply.
1, the domain is mebeli-ivanovi.bg. And make the inquiry form ask for a phone number.
Prefer to just write an email? Mail ai@openkbs.com and the Studio answers.
Mail coding,
questions answered
How fast is mail coding?
The first working version of a typical site or small app arrives within minutes of signing up. Changes you ask for by email usually come back in a few minutes too; bigger ones take longer and you get a mail when they are done.
What can it build?
Websites, online shops, internal tools, forms, dashboards, migrations from WordPress and other builders. It writes real code on real infrastructure: a database, hosting, email, your own domain. If something needs you to click in an app, the email tells you exactly where.
What does it cost?
Your first project starts free. After that you pay for the AI work in credits, with no subscription required. See pricing
Can I use the Studio too?
Yes. Every email carries a link to the same chat in the OpenKBS Studio, where you see the files, the preview and the history. Write there or reply by email, whichever is closer; the answer follows the channel you used last.
Your inbox is the whole workflow
Describe it once. Reply when you want something changed. The Studio does the rest and writes back.