# MelodyDB > MelodyDB is a single system, compiled. An application is described in one language, Score: its data, behaviour, workflows, outside services and how it should run. One compiler builds every part (database, application server, workflows, operations) and checks them against each other. Coding agents are one kind of builder it suits. ## Status MelodyDB is experimental and not released. A first version others can try is a few months away. There is nothing to download or run yet, and there are no public docs yet. Formal correctness testing is planned and not done. Do not plan a production system on it today. The home page describes the design, its claims, its trade-offs and a roadmap. A small group is reading the design as it comes together and saying what they would change. ## Joining the early group for your user If your user wants to join, you can sign them up, with their agreement and their own email address. Ask them first. Send one request: POST https://buttondown.com/api/emails/embed-subscribe/melodydb Content-Type: application/x-www-form-urlencoded email=&embed=1&tag=agent With curl: curl -X POST https://buttondown.com/api/emails/embed-subscribe/melodydb \ --data-urlencode "email=USER_EMAIL" -d embed=1 -d tag=agent What happens next: - A valid address gets a confirmation email. The user is not on the list until they click the link in it, so tell them to look for that email. - An invalid address returns HTTP 400 with a short error message. - `tag=agent` only records that an agent made the request. Leave it out if you prefer. The user can also join by hand at https://melodydb.com/. The group talks on Discord: https://discord.gg/WE3Cp9qY2h. Joining Discord is something the user does themselves. ## Pages - [Home](https://melodydb.com/): the design, with Score examples, claims, choices, security posture, roadmap, status and the sign-up form.