Why I Built GraceSoft Drawer: A Place to Put Things Down

For a long time, the things I wrote down didn’t really live anywhere.

A snippet of marketing copy sat in a message I’d sent to myself. A prompt I liked was buried in a notes app. Half a blog idea was in an email draft. A useful command was in a .txt file on my desktop called something like stuff-2.txt. Every time I needed one of them again, I’d spend a few minutes hunting across four different places, and sometimes I’d give up and rewrite it from scratch.

I didn’t need another workspace. I needed a drawer.

What I actually wanted

When I wrote down what I needed, the list was short:

• Dump text quickly. No templates, no databases, no setup. Open it, paste, done.
• Keep it somewhere private by default. My half-formed ideas aren’t anyone else’s business, and they definitely aren’t training data.
• Share a single piece when I want to. Send one text to someone without handing over everything else.
• Email it. Sometimes the fastest way to get text to someone (or to myself) is still an inbox.

That was it. Most tools I looked at either did far more than this, wrapped in features I’d never use, or did less than this while asking for more access to my data than I was comfortable with. So, being a developer with a studio and a slightly stubborn streak, I built it.

Why “Drawer”

The project started life as GraceSoft Scratchpad. It was a good working name, but there’s already a well-known Scratchpad out there, and I’d rather not build a product on top of a naming headache.

“Drawer” turned out to be a better fit anyway. A drawer is where you put things down so your hands are free again. You close it, and you trust that what’s inside will still be there later. Some drawers you lock. Some you open for someone else. That’s exactly how I wanted the product to feel.

Building it lean, on purpose

Drawer is built on GraceSoft Footing, the Laravel foundation I put together so that every new GraceSoft product starts from the same solid, security-conscious base. Because the groundwork (accounts, authentication, the boring-but-critical parts) was already in place, I could spend my time on the product itself instead of rebuilding plumbing.

The harder discipline was saying no. Every feature idea had to answer one question: does this make it easier to put text down, find it again, or share it? If not, it didn’t go in. Drawer is meant to stay small, and I think that’s a feature.

You decide what happens to each text

The one place I did add some structure is status. Every text in Drawer has one, so you’re always in control of who and what can see it:

• Draft — still being worked on.
• Private — just for you.
• Published — shareable with people you choose.
• Searchable — discoverable, for things you’re happy to put out there.
• AI Retrievable (paid) — text you explicitly allow to be pulled into your own AI context.

That last one matters to me. I’m wary of products that bolt “AI” onto everything to justify a higher price. In Drawer, AI access is opt-in, per text, and only for the texts you choose. Nothing is fed to AI by default.

Why I’m sharing it

Honestly, I built Drawer for myself first. I use it every day, and it has quietly replaced the pile of messages-to-self I used to rely on.

But if it’s useful to me, it’s probably useful to someone else who’s tired of their text being scattered everywhere. Offering it as a product also helps sustain GraceSoft as an independent studio, so I can keep building privacy-first tools that solve real problems rather than chasing hype.

If that sounds like you, I’d love for you to try it at drawer.gracesoft.dev. And if something feels off, or there’s one small thing that would make it better, tell me. That’s exactly the kind of feedback a small product like this is built on.

— D.L.