Devlog 006: Draftmount Is Finally Here

Hello again, writers!

Well. Here we are.

Five months ago, Draftmount was a collection of ideas, half-finished experiments and a frankly unreasonable number of browser tabs. Today it has a name, an identity, a website and an actual writing application. You can visit it at draftmount.com.

I’m still processing that myself. November has been about bringing everything together and getting Draftmount ready for its first writers, and since this is a development journal, here’s a look behind the scenes.

From prototype to actual product

For months I could test individual pieces in fairly controlled conditions. Now I’m looking at how everything behaves together, from opening the website and signing in to creating a project and actually writing something.

Something as simple as renaming a chapter involves more than changing a label. The interface has to reflect it, the project structure has to stay consistent, and the new name has to survive a refresh. There are a surprising number of ways for that to go sideways. Ask me how I know.

A little about the infrastructure

Draftmount runs in the browser, so I have to think about both what happens on your device and the services behind it. Cloudflare delivers the site and Firebase handles sign-in.

Signing in establishes who has access to an account, but that alone shouldn’t unlock every feature. This matters for beta access and, later, subscriptions, so I’ve kept those responsibilities clearly separate. That way the app can grow without account management turning into an enormous headache.

Let’s talk about manuscript storage

This is the most important limitation I want to be open about. At this stage, the writing workspace stores manuscripts in your browser, and they aren’t automatically synced to a cloud account. Clearing your browser’s site data, switching devices or hitting a storage problem can affect your work, so please keep your own exported backups during testing.

I’m careful about the next step because cloud sync raises questions that need deliberate answers. What happens when a writer edits the same chapter on two devices? Which version wins? What if the connection drops halfway through a save? How should the app recover from an interrupted operation? Those matter far more than adding a shiny cloud icon to the toolbar.

Beta access and feature entitlements

I’m taking a controlled approach to the beta so I can read feedback, chase down problems and make improvements without being overwhelmed. Invitations work through access codes tied to your account.

Beta testers get access to the Atelier plan, with features switching on as they’re ready during testing. Some of Atelier is still being built, so beta access doesn’t mean every planned premium feature is available on day one. I’d rather say that clearly now than have someone discover it after signing up.

Pricing and the long-term plan

I’ve settled the initial direction for Draftmount’s plans. Monthly pricing is:

• Essential: $4.99
• Studio: $8.99
• Atelier: $14.99

Each plan offers a different level of functionality, depending on what a writer actually needs, and I’m still refining how features are split while the beta runs. Pricing has to support development, infrastructure and support while still feeling fair to the people using the app. I’ll keep reviewing that balance as Draftmount grows.

A word about generative AI

Since this is a writing application, I want to be clear about one decision behind it: Draftmount is being built without generative AI writing features. Writers should stay in control of their stories, their creative choices and the words they put on the page.

That doesn’t rule out useful automation. Word counts, document organization, formatting and other conventional tools can make writing easier. The distinction matters to me, and I’ll keep explaining how each feature works as it arrives.

The website is live!

This has been one of my favorite parts of November. Draftmount finally has its own little home on the internet, with product information, pricing and an interactive writing page. I wanted visitors to get a feel for writing in Draftmount before committing to anything, and there’s something lovely about opening a website and immediately starting to type.

The site also tells Draftmount’s story and the values behind it. Draftmount is independently developed and queer-owned, and I’m proud to share that. I want the product to feel welcoming and thoughtful for writers with all kinds of experiences and creative processes.

What happens next?

For the rest of November, my priorities are the beta experience (editor reliability, exports and onboarding) and listening to writers who are meeting Draftmount for the first time.

As the person building it, I already know where everything is, which makes me a terrible judge of whether a button is easy to find. Fresh eyes are going to be invaluable. I’ll document known issues, review suggestions and share updates as things progress.

And yes, there will probably be bugs. I have yet to meet software immune to the little creatures.

Five months later

I started Draftmount in June 2026. Now it’s November, and I can finally start sharing it. That’s a strange and wonderful feeling.

I’ve learned a lot along the way, especially about managing scope, making technical decisions carefully, and recognizing when something needs more time. I’m an independent developer, and I want Draftmount to grow at a sustainable pace while getting the attention it deserves. There’s plenty more I want to build, and I’m excited to see how the studio changes once real writers start using it.

For now, I’m just very happy this little idea made it this far. Thank you for being here, and welcome to Draftmount.

Until the next draft,

The Draftmount Developer