Closing Tab One: Why We’re Sunsetting Sanctuary to Go All-In on Thermal

This morning, right in the middle of the live stream, I opened my Netlify dashboard, navigated to the settings for joinsanctuary.io, and paused the production deployments.

People were watching in the chat in real time as the original flagship of Martori Studio, the very first company I incorporated through Stripe Atlas back in May, the codebase that started this entire chapter of my life, officially went into the archive.

If you have been hanging out in the daily build-in-public streams on TikTok or Instagram over the last six months, you already know how much of myself I poured into Sanctuary. You watched me debug edge functions before sunrise with a cup of black coffee. You watched me obsess over the architecture, refine the Sovereign tier, and fight to prove that a solo technical founder in Nashville could build a massive, deeply human software platform from scratch.

Doing it live on stream made it real in a way I wasn’t totally prepared for. Walking away from your first project does not feel like a clean strategic pivot on a whiteboard. Honestly, it feels like a breakup. It feels like admitting that the thing that carried you through the darkest, most uncertain months of your year is not the thing that is going to carry you into the next one.

Nobody really talks about the pit in your stomach when you archive thousands of lines of code that you wrote while you were trying to put your life back together.

People talk about founder pivots on podcasts like they are cold, calculated chess moves. Here is the honest truth about why we closed the book on Sanctuary this morning, the hard data that forced my hand, and why Thermal (thermal-ai.app) is now the undisputed priority of Martori Studio.

The emotional armor of project one

To understand why it took me until late October to make this call, I have to be honest about what Sanctuary actually was for me.

Earlier this year, my life blew up. In the span of a few weeks in the spring, a relationship I thought was forever ended, and I walked away from my corporate job. Everything I thought my life was going to look like at thirty-four evaporated at once.

Building Sanctuary was how I got through the day. Every git commit was proof that I was still moving forward. When I filed the incorporation documents for SanctuaryApp, Inc. in May, it felt like planting a flag in the dirt and saying I was going to build a future on my own terms. And earlier this month, when I handed in my resignation at the agency to finally run Martori Studio full-time without a safety net, I carried this stubborn, romantic belief that a real founder never lets the original vision die.

When you build in public every single day, your ego gets dangerously tangled up in your roadmap. People show up in the stream chat at 7:00 AM asking how Sanctuary is doing. When you tell hundreds of strangers on the internet that a specific product is your flagship, pivoting away from it in front of them feels like standing under a spotlight and admitting you failed.

For months, the sheer act of shipping code gave me just enough validation to keep avoiding the hard truth. I kept telling myself we were just one feature or one UI polish away from an inflection point. I told myself that deferring active revenue was just part of a patient, disciplined rollout.

The numbers did not care about my nostalgia.

Then I stepped back and ran a brutal, unemotional due diligence audit across the entire Martori Studio portfolio.

The cold water of the audit

When you leave your day job and there is no W-2 paycheck coming in every two weeks, delusion becomes a luxury you cannot afford. You have to take off the creator hat and put on the capital allocator hat, especially when the capital you are allocating is your own sleep, runway, and mental bandwidth.

When I laid the audit data for Sanctuary right next to Thermal, the contrast hit me like a bucket of ice water.

With Sanctuary, our organic external traffic had completely flatlined. In both July and September, organic search clicks, external discovery calls, and unprompted inbound signups were sitting near zero. Every single ounce of activity on Sanctuary required me to manually push a boulder up a mountain on live streams. Furthermore, the platform carried a heavy infrastructure footprint, complex state management, and a high cognitive barrier to entry. We were asking users to change their daily behavior before they ever experienced the core value, which meant the runway required to make our Sovereign premium tier profitable was stretching out into the horizon.

Meanwhile, sitting in another window of Cursor, Thermal was doing the exact opposite. It was pulling us forward even when I was only giving it twenty percent of my attention.

I originally built Thermal to solve a very specific, exhausting bottleneck I kept seeing right here in Nashville: independent musicians are drowning in the business of being an artist. They spend thousands of hours and their last dollar perfecting a record, only to hit a brick wall when they realize they need Electronic Press Kits (EPKs), tailored PR pitches, social campaign copy, and cohesive brand assets just to get a playlist curator or venue booker to listen for thirty seconds.

Look at the actual evidence from our audit when we put Thermal into the wild:

1. 01

   Real, compounding revenue vs. theoretical projections

   While Sanctuary was still sitting at $0 in active recurring revenue, Thermal crossed into net-positive revenue back in July and has compounded its recurring paid subscriber base through August, September, and October. People did not just compliment the UI; they pulled out their credit cards and paid for it.

2. 02

   Frictionless unit economics and instant time-to-value

   Our pricing tiers ($8 a month for Solo and $20 a month for Pro, billed yearly) hit an immediate psychological sweet spot. To an independent artist or small manager, $8 to $20 is the cost of a couple of coffees or a pack of guitar strings, and it replaces hours of agonizing over press releases or paying thousands to a boutique PR firm. There is zero enterprise sales friction. An artist lands on the app, uploads a track, and gets a finished press kit in minutes.

3. 03

   A defensible technical moat: zero-upload local audio analysis

   The biggest pushback against AI in the creative community right now is fear and stigma. Musicians are terrified that uploading their unreleased masters to an AI platform means feeding their life’s work into a corporate training model. We engineered Thermal to solve this at the architecture level. Thermal uses privacy-first, local-browser audio analysis via the Web Audio API. Your audio file is analyzed right inside your own browser tab to extract sonic characteristics, tempo, and mood. The raw audio never has to live on an external AI training server. On top of that, because the heavy audio processing happens client-side on the user’s device, our cloud compute and bandwidth costs stay near zero. That gives us software margins approaching 90%+ even at an $8 price point.

4. 04

   Anti-slop positioning

   We stripped out all the generic, glossy AI wrapper tropes and rebuilt Thermal around a “stripped core” technical aesthetic. Thermal does not generate fake music or try to replace the artist. It acts as an automated record label marketing department so the human can go back to making art.

5. 05

   Organic technical health

   Even while pushing rapid CI/CD updates and refining our conversion funnels, thermal-ai.app maintained a 93% Site Health score in our technical SEO and infrastructure audits, giving us a clean, fast foundation that search engines and users actually trust.

When we looked at those numbers on stream this morning, I couldn’t hide behind the nostalgia anymore.

If you never go all-in on the thing that is actually working, you never have to find out how big it can really get.

I realized I was using my attachment to Sanctuary as an excuse to play it safe.

The fallacy of the nine-app studio

For the last few months, I wore the size of the Martori Studio ecosystem like a badge of honor. Sanctuary, Thermal, Datum, Nash Hat, Ledger...

With modern AI-assisted development, React, Vite, Tailwind, Supabase, and Netlify, a single technical founder can spin up production-grade software at a velocity that used to require a ten-person engineering team and a seed round. It is intoxicating. When you get stuck on a hard marketing or distribution problem on App A, it is so easy to open a new repository and get the cheap dopamine hit of building App B.

I have to call myself out on that. Just because you can build nine products at once does not mean you can scale nine products at once.

Code is no longer the bottleneck in 2026.

Attention, trust, retention, and distribution are the bottlenecks.

Every hour I spent refactoring a component in Sanctuary was an hour I was not fixing a broken CI pipeline in Thermal, optimizing our landing-to-checkout handoff, improving our Core Web Vitals, or sitting down with independent artists and managers here in Nashville to make the product undeniable. I was spreading my energy thin and calling it ambition.

What happens now

Sanctuary was not a mistake. Without the hundreds of late-night hours I spent building it from scratch, Martori Studio would not exist. I would not have the reusable authentication flows, the deployment pipelines, or the sheer operational grit that allowed me to build Thermal so quickly. Every hard lesson I learned in Sanctuary is already living inside Thermal’s codebase.

We wound down joinsanctuary.io with respect today. The repositories are safely archived, the production builds are paused, and I am finally letting myself close that mental tab.

Starting right now, Thermal is the singular priority of Martori Studio.

When you tune into the late-night stream tonight or the morning sessions the rest of this week, you are going to see a much sharper, more focused version of this journey:

• Obsessing over the conversion funnel

  We are tracking every single step of the user journey, from the moment an artist lands on thermal-ai.app, to the local-browser audio scan, to the moment they upgrade to Solo ($8) or Pro ($20).

• Conquering the churn problem

  Our due diligence audit highlighted our biggest real risk: music releases are cyclical. Artists tend to subscribe when they drop a single and cancel a month later. Over the next thirty days, we are engineering continuous release-cycle workflows and catalog-management features so Thermal becomes a year-round operating system for an artist’s career, not just a launch-day utility.

• Grassroots distribution in Music City

  I live in Nashville. Instead of just shouting into the algorithm, I am taking Thermal directly to the independent artists, producers, and boutique managers who need this most.

Project One kept me going when I had nothing else, and it deserves a proper send-off. Now we come back to the desk, and we put every ounce of our firepower behind the product that is already working.

Brian, Nashville