Today I got an email announcing the end of val.town, one of my favorite recent companies to exist. I'm not quite sure what to think - the company always felt a bit rudderless to me, the value proposition being to provide a deceptively simple trigger-based program execution platform with lightweight storage. To me, this has clear utility, and I used it often when I needed something that lived between durability and convenience. A fantastic prototype tool, but hard to understand the systemic value of, especially in the context of a larger project.

I'd love to talk more with the team behind val.town and hear how things looked from their end, but I also find some value in analyzing what went well and what went poorly from the outside as a lurker/fan.

Something I really admired about the team was how well they did outreach - the product is admittedly fairly opaque, so they sent emails that kind of simultaneously justified their existence and created space for exploration around their product. The brand identity was always very strong for me in a positive way, I feel like I was rooting for them from the first time I played with it. Very twitch, and perhaps a lesson in and of itself, as they now experience an unceremonious twitch-like end.

Why didn't val town resonate? One thought could be that they leaned too heavily on the "AI will fix it" angle of software engineering problems - something I'm trying to learn from and pay attention to as I resist a similar temptation with archival's task mode. Townie seemed useful but admittedly I never used it. I either wrote my Vals by hand or delegated to Claude. But I also wanted, and failed, to use the platform more often. It's possible that the scope of the product lacked ambition, in a time where folks already feel either empowered or alienated by AI. Within a short timeline of months, I personally went from feeling like Townie was brilliant to feeling like it was redundant. It's clear to me now that tools will need to meet people where they are and have a clear purpose when presented in-product.

But if there's any clear takeaway for me, it's that good, noble, useful products like this cannot live in a world of venture capital. Despite their amazing brand identity, their focus on enablement and personality, their growth goals clearly limited their ability to achieve exit velocity. Why did they raise? I wish I knew. At Archival we deploy similar infrastructure and have capital demands that won't ever require debt - but we also are paying for our own mortgages from our savings - I could believe that it was an impossibility for the product to exist as easily as I could that it was a cargo-culted industry expectation that debt creates validation.

Ultimately, I mourn the death of a genuinely useful, innovative, and productive platform that I saw lots of value in, while recognizing that the enemy of something wonderful is often time, and by raising capital they bargained their time foolishly. I hope to have an opportunity to understand their trajectory better someday.

Archival's sql carriers features do much of what Val town did. Before I built it, I would use val town for lightweight distributed stateful APIs, so a lot of what worked there now works here. I'd love to help any folks who would like a forever promise move over - we have no debt and no free tier, a trade off that I hope will become more pervasive in the future - but mostly I'm excited to see what Steve and the team bounce back with. I'm not sure Archival would be what it is today without seeing the example of a truly curious and human product like val town make it so far.