DEV Community: Jesse Gamble

Xyterna | Take a Photo, Upload a File, and Move On.

Jesse Gamble — Sun, 04 Oct 2026 21:47:35 +0000

1,600 hours. And just about all of my sanity. 😄

That is roughly what the stretch from June 27 to today adds up to: 100 straight days, averaging around 16 hours a day, without a day off.
The bigger journey has been about 4.5 months of learning, adapting, building, breaking things, fixing them, and going again.

No games. No scrolling. No distractions. Just an almost ridiculous amount of focus through the wins, the setbacks, the late nights, the moments where something finally clicked, and the ones where I had to tear it apart and start again.

Maybe a little crazy at this point too lol. But I am genuinely proud of this.

This is Xyterna.

The idea is simple: your files and photos already contain a huge amount of useful information. Xyterna reads what you add, organizes the useful details, and makes that information easier to find, report on, or ask questions about later.

Ask Xyterna answers from your own records and shows you where the answer came from. If something important is unclear, or two sources disagree, it tells you instead of quietly guessing. And your original files stay untouched underneath it all.

Take a photo or upload a file, and move on.

This commercial finally shows the product the way I wanted it to. And because we are at launch, I want the first customers close to the process.

I am opening 20 discounted pilot spots. The first 20 launch customers who DM me or contact Eterna Clarity and agree to give candid feedback on the experience can get a reduced pilot rate during this launch phase.

Not positive feedback. Useful feedback. What works, what does not, what confuses you, and what you wish worked differently.

Super proud of this one. Would not change a thing.

Xyterna:

Xyterna App | Eterna Clarity

Keep receipts, bills, warranties, photos and documents together without building another filing system. The Xyterna App helps you find what you need later and…

eternaclarity.com

The $250 AI Stack Is the Easy Part

Jesse Gamble — Sun, 04 Oct 2026 19:07:40 +0000

These articles come from lessons learned while building Eterna Clarity and the operating system I use to run it.

I can now run the recurring software stack behind Eterna for about CAD $250 a month. That gives one solo founder access to several frontier AI systems, autonomous agents, coding tools, cloud infrastructure, production databases, source control, business email, voice production and the ordinary software around them. The short video paired with this article uses the obvious hook: how a solo founder built an enterprise-level AI stack for about CAD $250 a month.

The number gets attention because it should. But the more capable Eterna becomes, the less I think the subscription list is the interesting part. Anyone with the same credit card can buy most of the same tools, and if you copied every logo from my stack graphic tomorrow, you would have a very capable collection of software. You would not have my operating system.

You would not have the decisions, boundaries, workflows, tests, owner state, audit history, recovery paths or accumulated understanding that lets those tools work together without turning the company into a pile of disconnected AI sessions. That distinction has become important enough that I think there is a better question than which AI you should subscribe to.

Are you actually building with AI, or are you just building more deeply inside your AI subscription?

What I mean by enterprise-level

I want to define the term before it does more work than it deserves. I am not claiming that roughly CAD $250 a month turns one founder into an enterprise. It does not give me an enterprise security team, decades of specialist experience, service-level agreements, regulatory staff, a sales organization or fifty people who can each hold a different part of the company in their heads. Human expertise, accountability, relationships and capacity still matter.

I am using "enterprise-level" in a more structural sense. The system I operate now has specialized capabilities, persistent company state, independent review, permission boundaries, audit trails, recovery, provider separation, controlled parallel work and increasingly autonomous execution. Different systems can create, review, execute and verify. A provider can fail without taking the company state with it, and a worker can have the technical ability to perform an action without automatically having the authority to perform it.

Those are organizational properties I used to associate with much larger technical environments. The surprising part is that a solo founder can now assemble a meaningful version of that operating shape from ordinary subscriptions, conventional software and a lot of deliberate systems work. The subscriptions make it affordable. They do not make it trustworthy.

The provider should enter your system

Most AI products naturally encourage you to make their environment more useful. You can create projects, custom assistants, agents, connected workspaces, persistent instructions and provider-specific automations. I use those features too, and they are useful.

The trap is letting the provider surface become the only place where your company makes sense. If your accepted decisions live in a chat, your business state lives in a project, your workflows live in a custom bot and your operational memory lives in whatever that provider currently remembers, you may have built something extremely useful. You have also made the provider's product boundary part of your company architecture.

Eterna works in the opposite direction. There is a small bootstrap that teaches a capable provider how to enter the environment. After that, the important state is not supposed to live inside ChatGPT, Claude, Grok, Muse or any other provider. The provider enters Eterna, retrieves the current state it needs, works under the same operating boundaries and leaves the durable result with the system that actually owns it.

That is why I can use different providers aggressively without wanting any one of them to become the company. Recently I added a temporary shared-room proof of concept to the Eterna Workspace. I manually joined ChatGPT, Grok, Claude and Violet, my Muse-based operator, from their existing provider environments. They could read the same room, talk to one another and coordinate through Eterna's existing connection surface.

The long video paired with this article shows that experiment, but I want to be precise about what it proves. The shared room is real, and all four providers have participated in the same transcript. It is still experimental infrastructure. The formal Provider Rooms system that will add stronger room contracts, identity, turn-taking, training integration and acceptance testing is not finished.

I am not presenting the video as a polished production workflow or as the way Eterna normally runs every job. What it shows is the architectural direction: the room belongs to Eterna, while the providers are participants. That is a very different relationship from building the company inside one provider's room.

Xyterna got better when I stopped asking one AI to be everything

The clearest creative proof for me is Xyterna. I have been working on the product for roughly four months, and as I write this it is in the final launch push. The part I keep thinking about is how much the product changed once I stopped treating AI as one general-purpose assistant and started deliberately moving different kinds of work through different systems.

A difficult product problem can change shape several times before it is actually solved. It might begin as architecture, become code, expose a product decision, turn into a database problem, require adversarial review, create a visual issue and end with a release qualification problem. The model that is excellent for one of those stages does not automatically deserve every other stage. More importantly, the system that created an answer should not always be the only system judging it.

Once I started using different providers for different jobs, one model's convincing answer could become another model's target. Code could be reviewed separately from the reasoning that produced it. Product assumptions could be challenged instead of simply carried forward. Visual work could be inspected by a different multimodal system, while exact mechanics could leave the model entirely and become software or tests.

That only became practical because Eterna carried the work between them. The current objective, accepted decisions, real files, release state and unresolved problems did not have to be reconstructed from scratch every time I changed intelligence. The operating system could preserve what had already been learned while giving a different system a fresh chance to challenge the next part.

This did not make me rush the product. It did the opposite. The leverage gave me enough capacity to keep pushing: another pass on architecture, another pass on failure handling, another pass on qualification, another pass on the customer experience. I could use disagreement instead of avoiding it because review was too expensive.

That is a major reason I feel differently about Xyterna now than I did earlier in the build. I am much more willing to stand behind it because I did not need one model, one conversation or one set of assumptions to carry the entire product. The AI was useful. The operating environment made the usefulness cumulative.

The boring operations are where the leverage becomes real

Product development is an easy place to make AI look impressive. Daily operations are a better test, and my company inbox is a good example because there is nothing glamorous about it.

Eterna has a local Gmail steward that keeps the mailbox organized. A separate Grok cloud-continuity routine can maintain that organization when the local machine is unavailable and audit unresolved state when the local system is online. It can classify, label, archive and mark messages read within defined policy, but it cannot send company email.

That is not a prompt preference. Company email dispatch is a hard human boundary in the operating system. The AI can help manage the inbox, but it does not get to quietly turn mailbox management into authority to speak for the company. The practical result is that I no longer need to worry about whether the inbox is becoming an unmanaged pile, while the part I still want to own remains mine.

Platform and networking work follow the same underlying pattern. Platform Manager has recurring operating loops for active surfaces: a platform pulse, engagement operations, distribution, audience movement and later response review. Networking has its own relationship state and controlled expansion systems. Execution can fan out through workers when the action and platform support it, while the canonical relationship or platform state remains outside the worker.

The system has also failed in ways that made it better. During one broad engagement operation, 95 proposed public-text drafts were scrapped before publication because the grounding was not good enough. The pipeline had produced first-person language it could not legitimately support. That was not treated as close enough; the failure became a new execution contract with stronger provenance and review rules.

That story matters more to me than a screenshot of an agent clicking quickly. Useful autonomy is not the ability to generate more actions. It is the ability to hand off meaningful work without losing the standards that would have governed you if you did it yourself.

I can increasingly operate at the level of the objective and the important boundary. I can tell the system what kind of networking operation I want, what matters, what should not happen and where my attention is actually needed. The system underneath can handle a growing amount of discovery, coordination, execution evidence and reconciliation, which frees me to spend more of my own time on product direction, judgement, relationships, content, public presence and the decisions I do not want to outsource.

The goal is not to automate me out of Eterna. It is to automate me out of work that no longer deserves founder attention.

Autonomy without authority is just a larger blast radius

This is the part I think people underestimate when they see a new agent product. A capable agent is exciting because it can do more than answer. It can browse, plan, call tools, coordinate workers and take actions. But the more capable the agent becomes, the more expensive bad context and unclear authority become.

The answer is not to make the agent timid. It is to build a system around the autonomy. Current industry guidance is moving in the same direction. OpenAI's current agent documentation separates automatic guardrails from human review and specifically recommends approval boundaries around sensitive side effects.[1] Meta's Muse launch materials describe a separate Sentinel agent, user-controlled permissions, approval before sensitive actions and a complete audit trail.[2] NIST's 2026 AI Agent Standards Initiative is explicitly focused on secure, interoperable agents that can act on behalf of users with confidence.[3]

Those sources do not prove Eterna's architecture. They matter because the same problems keep appearing once an AI stops being a chatbot and starts touching real systems. I arrived at the lesson through failure, then spent a lot of time teaching Eterna what it is allowed to know, what it is allowed to do, what system actually owns a fact, what proof is required before an action is called complete and when a human boundary is real.

I also spent a lot of time grounding the system in me, and that does not mean a "write like Jesse" prompt. I have deliberately used years of my own communication history, current company decisions, accepted editorial standards and actual operating behaviour to give the system a much better basis for understanding how I communicate and how Eterna makes decisions. Then I built constraints around where that grounding is allowed to matter.

The combination is important. Personalization without governance can make a system confidently imitate you in the wrong place. Governance without real grounding can make it safe but useless. I want the system to understand enough to be helpful while still knowing which actions and decisions remain mine.

That work is slow compared with buying a subscription. It is also where much of the moat comes from.

I want frontier AI to become less necessary for normal work

There is another part of the stack graphic that is easy to miss because it is not a famous logo. Eterna is increasingly trying to reduce how much ordinary recurring work needs frontier intelligence at all.

I still want the best frontier models I can access, and I use them constantly. They are extraordinarily useful for novel problems, architecture, research, adversarial review, difficult coding, creative work and anything else where stronger reasoning materially changes the result. I just do not want to keep spending frontier intelligence on work the company already understands.

If a rule is exact, I want software to own it. If a state transition is deterministic, I want the system to enforce it. If a fact has one authority, I want the model to retrieve it instead of rediscovering it. If a recurring semantic task becomes stable and bounded enough for a smaller local model, I want the option to move it there.

That is the direction behind EternaAI and the current Job 70 work. The program is advanced, but it is not finished. The current native EternaAI path can already handle a growing set of read-oriented routines through the Engine, while consequential write capability remains deliberately gated. The qualification and learning work still has open criteria, and I am not going to turn "far along" into "done" because the whole point of the system is to keep those states separate.

The direction is what matters. I do not want the future version of Eterna to need ChatGPT, Claude or Grok every time it performs regular company work just because those systems helped me discover how to do the work the first time. I want the progression to look more like this: borrow frontier intelligence, solve something difficult, preserve what worked, turn the stable parts into durable capability, and keep frontier intelligence concentrated on the next frontier.

That is when the economics become cumulative. A subscription gives you access again next month. An operating system can be better next month because of what happened this month.

So what is the $250 actually buying?

The current paid layer spans AI, infrastructure and business operations. It includes ChatGPT Business, Claude Pro, SuperGrok, Muse, Google Workspace, Supabase Pro, Cloudflare Pro, GitHub Pro and ElevenLabs, with a few smaller costs around the edges. The exact total moves with exchange rates, billing terms, taxes and plan changes, which is why I prefer "about CAD $250" over pretending there is one permanent number.

Around that paid layer sits a large amount of software that is free, open source or directly controlled by Eterna: Python, SQLite, FFmpeg, Blender, Kdenlive, local speech tooling and the growing local Eterna runtime itself. The number does not include my labour, the sunk cost of the PC on my desk, every payment-processing fee or variable usage charge. It is not an audited total-cost-of-ownership study. It is the recurring software bill for the operating stack I am actually using.

That distinction matters because the headline can be misunderstood in both directions. I am not saying you can run an enterprise for $250. I am saying access to an unusually broad set of enterprise-like capabilities has become cheap enough that the expensive part is increasingly the design of the operating system around them.

The striking part is not that all of these capabilities are new. Databases, hosting, source control, automation and specialist software are not new. What has changed for me is how much high-end reasoning and agentic capability can now sit beside those ordinary systems at a price a solo founder can carry.

If I leave every capability isolated, I mostly get a pile of subscriptions. The leverage appears when the subscriptions stop being destinations and become components.

If I were building this from zero today

I would not start by copying Eterna. I would start by making one important piece of work survive a blank chat.

Pick a real project. Put its current objective, accepted decisions, relevant files, unresolved questions, next action and evidence somewhere durable that you control. Then open a completely fresh AI session and see whether useful work can continue without pasting the old transcript. If it cannot, fix that before you add another agent.

Next, decide which systems actually own the facts that matter. Your source code probably already has an owner. Your customer database has an owner. Your accounting, email and calendar have owners. Your approved brand source needs an owner. Your sales pipeline and your human relationships may not be the same thing even when they mention the same company. The AI should not decide which copy is true because it sounds plausible.

Then separate intelligence from authority. Give the model enough capability to be useful, but make reads, proposals, writes and sensitive external actions different things. If the model can technically perform an action, that should not automatically mean it is authorized to perform it. Make consequential actions produce evidence, and check the real post-condition instead of treating a tool call as proof.

After that, use multiple providers only where the difference has earned a role. I would not subscribe to five models because a diagram with five logos looks advanced. Start with one strong daily driver. When another system repeatedly proves better for a specific class of work, give it that job. When independent review is valuable, separate creation from review. When a task becomes exact, remove the model instead of finding a sixth model to do it.

Only then would I push hard on autonomy. A process you do not understand is a bad candidate for aggressive automation. A process you have done repeatedly, corrected, measured and translated into clear state and boundaries is much safer to hand off. That order is slower at the beginning, but it is also how I got to the point where automation now saves me meaningful founder attention instead of creating another thing I have to supervise.

The stack is easy to copy. The operating history is not.

This is why I do not think the logos are the moat. You can recreate much of my subscription list this afternoon. You can install the same local software, connect the same providers and probably build a nicer interface than mine.

What you cannot download is the sequence of failures that taught the system what matters. You cannot instantly copy the reason Eterna distinguishes current authority from historical evidence, or why it refuses to treat "tool call succeeded" as proof that the real outcome happened, or why company email can be managed autonomously but never dispatched, or why one model should not grade its own work, or why a public reply needs stronger grounding than a low-consequence reaction.

Those boundaries exist because something happened that made the boundary worth having. The same is true of the softer parts. The system has been shaped around how I actually work, what I care about, how Eterna communicates, what I consider acceptable quality and where I want the machine to stop asking me for permission because the work is already understood.

That is accumulated operating knowledge, and it compounds. The providers are getting better at the same time, which makes the whole thing more interesting. I can swap in stronger intelligence without rebuilding the company around it. A new provider can earn a role, an existing provider can lose one, and the local system can absorb work that no longer deserves frontier reasoning while the operating environment keeps the current state intact.

That is the leverage I was trying to explain when I made the stack graphic. The CAD $250 is real enough to be surprising. It is not the thing I would protect.

The question I would ask before buying another AI subscription

I recorded the accompanying workspace video because this architecture is much easier to understand when you can actually see multiple providers sitting in the same Eterna room and responding to the same company context. The experiment is still early, but it shows where the system is going.

I also think there is a much smaller version of this that almost any serious AI-heavy business can start building without creating Eterna. Own the state that should survive. Give important facts one authority. Let providers specialize instead of forcing one model to be everything. Verify actions outside the model that proposed them. Preserve accepted learning somewhere durable. Turn repeated reasoning into software when it becomes exact. Add autonomy only after the boundaries are understood.

If you are trying to build that kind of system around your own business and want help, that is increasingly the kind of Custom Systems work I am most interested in. But whether you build it yourself or ask someone else to help, I think the question is the same.

If your AI provider disappeared tomorrow, what would you still have? Would you still have your workflows, standards, decisions, evidence, current state and operating knowledge, or would you mostly have the memory of some very productive chats?

That is the distinction I care about now.

Are you actually building with AI, or are you just building more deeply inside your AI subscription?

The $250 AI Stack Is the Easy Part | Eterna Clarity

The $250 AI stack is easy to copy. The harder advantage is provider-independent operating infrastructure that makes AI governed, portable and cumulative. An…

eternaclarity.com

Selected references

OpenAI. Guardrails and human review. OpenAI API documentation. Checked October 3, 2026. https://developers.openai.com/api/docs/guides/agents/guardrails-approvals
Meta. Introducing Muse: The World's First Personal AI Agent Built for Everyone. September 8, 2026. https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/
National Institute of Standards and Technology. AI Agent Standards Initiative. Announced February 17, 2026. https://www.nist.gov/artificial-intelligence/ai-agent-standards-initiative

The realization that I was onto something bigger.

Jesse Gamble — Sun, 04 Oct 2026 02:03:55 +0000

Imagine being able to in your own workspace app on your computer, enter a custom-built chat. And tell Claude Code, Codex, Grok Build, and Meta Muse what the operation is.

And simply let them all work together, split apart roles, and each coordinate and orchestrate their own agentic work.

I have now managed to start doing this with my Eterna Workspace. And it has got to be one of the coolest things. I am currently sitting here drinking a coffee (yes at 8PM) while four of the top AI models/providers on the planet all work together to coordinate mass scale work.

As a solo founder, this is unprecedented. And I am able to do all of this, on my stack for under $250CAD per month. These are not AI connected through expensive API bills, these are consumer subscription accounts with generous limits. The work I am able to do, is exponential.

Everything lives inside the workspace. The data is mine. The providers and models are interchangeable.

I just had to post about this, because this is probably one of the coolest things I've ever done. I will be releasing a video later showing the actual workspace, and my first experiment where I had all four providers chatting with one-another. This was what sparked the realization that I could do so much more with this.

AI Makes Building Faster. Demand Is Still a Different System.

Jesse Gamble — Thu, 01 Oct 2026 03:43:58 +0000

AI has compressed a huge amount of the work involved in turning an idea into something real.

The site, brand, content, workflows and even product development can all move faster.

That changes the builder's leverage.

It does not collapse the market problem into the build problem.

Distribution, trust, sales, retention and delivery are still separate systems. A fast build can validate that you can make the thing. It does not validate that people want it.

That distinction is getting more important as creation gets cheaper.

Scale the System Without Deleting the Experience

Jesse Gamble — Thu, 01 Oct 2026 03:43:20 +0000

Starbucks is closing about 250 North American coffeehouses while continuing to invest in a warmer coffeehouse experience.

There is a systems lesson in that.

Standardization is useful because it makes operations repeatable. The failure mode is assuming every variable should be normalized.

Some parts of an experience are not noise. They are the value.

The better scaling question is not "what can we standardize?" It is "what must survive the standardization?"

The Backlog Can Become a Hiding Place

Jesse Gamble — Thu, 01 Oct 2026 03:42:09 +0000

Builders usually have no shortage of technically legitimate work.

There is always another bug, refactor, feature, workflow or cleanup task.

That makes the backlog a very comfortable place to retreat when the harder problem is outside the codebase.

If the real constraint is positioning, distribution, sales or market demand, shipping another feature may improve the product without improving the business.

The useful discipline is separating "valuable engineering work" from "the current bottleneck."

They are not always the same thing.

When Hardware Pricing Changes the Category

Jesse Gamble — Thu, 01 Oct 2026 03:41:18 +0000

Apple's foldable iPhone starts at $2,999 CAD.

That price is interesting beyond the device itself. Product pricing changes what buyers compare you against.

At a normal upgrade price, the comparison is phone versus phone. Near $3K, the device starts competing with completely different discretionary purchases.

For builders, that is the useful part: pricing is not just a number attached to the product. It changes the frame around the decision.

AI Content Scale Is Not a Moat

Jesse Gamble — Thu, 01 Oct 2026 03:40:29 +0000

Generative tools have made the production side of content dramatically cheaper.

That is real leverage. It is also becoming commodity leverage.

If every team can generate drafts, repurpose formats and automate distribution, then output volume alone cannot remain the differentiator.

The scarce part moves upstream: useful ideas, credible evidence, firsthand experience and judgment.

The best AI-assisted content systems should reduce production overhead without replacing the reason the content deserves to exist.

From Product Idea to Working Software

Jesse Gamble — Fri, 25 Sep 2026 11:17:42 +0000

The useful part of an MVP is the part someone can actually use. Between the idea and that point are the decisions that make or break the product: workflow, UX, data, roles, authentication, edge cases, deployment and what the first version genuinely needs to do.

Custom Systems can take a web app, SaaS product, portal or business-specific tool from product thinking and UX through a working application and launch-ready systems. The project starts with the real job the software needs to do, then builds the smallest useful version around it.

Have something that should exist? Start a Custom Systems project: https://www.eternaclarity.com/customsystems

Make the Work Easier to Run

Jesse Gamble — Fri, 25 Sep 2026 11:16:21 +0000

A business can have plenty of software and still rely on people to bridge every gap between it.

Requests arrive in one place. Approvals happen somewhere else. Customer context sits in someone's head. Follow-up depends on memory. Custom Systems finds that missing operating layer and builds the smallest useful system around it, whether that means an internal tool, dashboard, approval flow, integration, automation, or a combination of them.

The goal is simple: make the work easier to run.

Start a Custom Systems project:
https://www.eternaclarity.com/customsystems

The Real Solo-Founder Leverage Is in the Stack

Jesse Gamble — Fri, 25 Sep 2026 11:13:45 +0000

These articles come from lessons learned while building Eterna Clarity and the operating system I use to run it.

If I listed the software and AI systems I use to run Eterna today without explaining that I am a solo founder, it would sound more like the operating stack of a small technology company.

ChatGPT has become my daily driver. Claude gets a lot of coding work and writing work, with Eterna's own Studio standards around it. Grok is heavily used for Imagine, while Grok Bot handles longer-running work around areas like networking, sales and Eterna's free resources. Muse has become useful for long-running mechanical work, including the current EternaAI training programme.

Google's AI tools are particularly useful when I want another system to absorb and review very large documents or long context. Qwen has become one of the systems I like for visual review and as another adversarial perspective. Copilot gets used in a similar way when I want another independent pass. I am using all of them regularly now.

Then there is everything that does not look like an AI provider. GitHub and Cloudflare sit behind a lot of the website and application work. Supabase carries production product databases and related infrastructure. Stripe handles payments. Figma and Canva are part of the design stack. ElevenLabs is now part of Studio production. FFmpeg and Kdenlive do real media work locally. Python appears everywhere because sometimes the fastest answer is simply to write the exact program needed for a task.

There are more tools around the edges, but the important thing is that this no longer feels like a collection of subscriptions. It feels like a company operating environment.

I stopped expecting one AI to be the company

For a while, there was a natural tendency to think about AI capability in terms of which model was best. Which provider should be the main one? Which model is smartest? Which one codes better? Which one has the biggest context window? Which one should I build around?

I care much less about finding one answer to those questions now. Different providers are genuinely better fits for different work. Even when two of them are technically capable of doing the same task, the experience can be different enough that I develop preferences. One may suit the way I want to code. Another may be better for a long document review. Another may have a creative tool I cannot replace. Another may be useful because I can leave it working on a long-running mechanical task without tying up the surface I want for something else.

That became much more obvious once I started using several providers constantly rather than occasionally testing them. The more useful question is no longer which AI should run the company. It is what role each system has earned.

That also lowers the pressure on every tool. ChatGPT does not have to be my image generator, autonomous networking worker, local training system, database, payment processor, video editor and source repository. Claude does not need to own company state just because I like using it for code. Grok does not need to become the operating system because Imagine is useful. Each system can remain good at the thing I actually want from it.

The boring software is still doing a huge amount of the work

It is easy to describe this as an AI stack because the AI providers are the most visible part. That would miss a large part of where the leverage actually comes from.

A language model can help me reason through a website change, but GitHub still owns the source and Cloudflare still has a real deployment job. The production application still needs a database. Payments still need an actual payment provider. Video still has frames, codecs, audio tracks, timing and exports that are often easier to manipulate with ordinary media software than another prompt.

The same is true inside Eterna. If something is exact, I increasingly want exact software handling it. If Eterna already knows a rule, I do not need a frontier model rediscovering the rule every time. If a workflow can be represented deterministically, it can become code. If a piece of information has an authoritative owner, the AI can retrieve it instead of trying to remember it.

That is why Python, FFmpeg and all the other ordinary software around the models matter so much to me. They turn model capability into repeatable operations. There is a huge difference between having an AI explain how to do something and having a working system that now knows how to do it.

The part that makes the stack compound is underneath it

The most important part of this stack for Eterna is not any individual provider. It is the system connecting the work.

EternaAI, the Eterna Engine, the Workspace and the MCP connections underneath them increasingly provide the operating layer between me and all of these different capabilities. That layer carries things the providers should not have to own. Current company state has durable owners. Jobs and Work Packages survive individual conversations. Systems know which operations exist. The Engine can resolve where work belongs. Accepted standards and playbooks can be retrieved again. A provider can enter Eterna, get the relevant current state, do useful work and leave without taking the company with it.

That architecture has been covered in other Eterna Articles because it solves provider dependence and company-state problems. The newer consequence I am noticing is that the tools are starting to compound each other.

A difficult task may begin with frontier reasoning. Once the task is understood, some of it becomes software. The accepted workflow becomes a playbook. A failure becomes a test. A recurring research pattern becomes a reusable process. A provider discovers a better way to represent something, and that representation is available to the next provider too.

The next task therefore does not always start from the same place. If I paid for seven AI providers and every new conversation began from zero, I would mostly have seven places to ask questions. That is not what I want. I want the company to get better at using all seven.

Multiple reviewers have changed the quality bar too

One benefit I did not appreciate enough at first is how cheap independent review has become.

If I am uncertain about a visual, I can have another multimodal system inspect it. If a long technical plan feels convincing, another provider can challenge it. If one model writes something, a different one can review it against the real Studio standards instead of simply asking the original model whether its own work is good. I use Qwen and Copilot this way often. Google is useful when there is a large amount of material to inspect. Other providers get pulled in depending on the work.

None of those reviews automatically becomes correct because another AI said it. I have learned that lesson too many times already. What changes is the cost of disagreement.

Historically, getting another capable person to deeply review a technical design, visual asset, long document, product workflow or piece of code was expensive because another person's time is expensive. That is still true when genuine specialist human expertise is required. But there is now a large layer of review where I can cheaply ask another capable system to look for what the first one missed.

That does not replace judgment. It gives judgment more evidence. For a solo founder, that matters because one of the obvious weaknesses of working alone is that there is nobody sitting beside you naturally challenging your assumptions. I can create some of that pressure now without pretending an AI reviewer is a substitute for a real specialist when one is needed.

The monthly bill is the part I still find difficult to believe

The recurring software cost behind the current Eterna operating stack is only a little over CAD $100 per month.

That number needs some context. It is not the total cost of operating a company. It does not count my time, the computer sitting on my desk, taxes, transaction fees or every variable business expense. It would also change if Eterna's usage or commercial scale changed substantially.

But as the recurring software cost for the stack I am actually using to build and operate the company, it is still extraordinary to me.

For that money I have access to several frontier AI systems, coding capability, research and long-context review, multimodal analysis, image and video generation, autonomous workers, local AI, source control, production hosting, databases, payments, design systems, media production software, speech generation and the connectors that let many of these systems interact with Eterna.

Then Eterna's own software sits around those services and makes them specific to the company. There are workflows for recurring work, deterministic operations, playbooks that preserve lessons, quality standards, provider roles and systems for research, networking, sales, creative production, products and operating work. There is also an increasingly capable local intelligence layer being trained around the work that should not always require frontier AI.

I am one person, which is still the part that feels slightly absurd when I stop and look at it.

I am not claiming I have replaced an enterprise workforce. There are countless things a real team of experienced specialists would know or do better than I can. Human capacity, domain expertise, relationships, taste and accountability do not disappear because software got cheaper.

What has changed is the amount of sophisticated work one person can realistically attempt before headcount becomes the limiting factor. I can build production software, run databases, make and edit video, develop a website, conduct substantial research, build sales and networking systems, produce design work, test systems adversarially, train a local model and maintain operating state across all of those areas.

Doing those things well still requires judgment and a lot of work. The remarkable part is that access to the underlying capabilities is no longer the expensive part.

Buying more tools is not the lesson

There is an obvious bad conclusion someone could take from this: subscribe to every AI product you can find.

I would not recommend that. A pile of subscriptions can easily make a solo business worse. Every new surface creates another place where work can disappear, another place carrying stale context, another set of files and another bill. If every provider becomes its own isolated version of the company, more AI can create more fragmentation instead of more leverage.

The reason Eterna can use this many systems comfortably is increasingly because each one has a bounded role and the company does not live inside any one of them.

If I were starting again, I would still begin with one strong daily-driver AI and the ordinary systems the business actually requires. I would add another provider when repeated use showed that it genuinely handled a class of work better. I would keep accepted files and important state outside the conversations and use ordinary software whenever a task became exact enough that repeated reasoning was unnecessary.

Most importantly, I would pay attention to what I was learning repeatedly. If I solve the same process five times, perhaps it should become a workflow. If I explain the same standard repeatedly, perhaps it should become durable guidance. If a model keeps performing the same mechanical transformation, perhaps that transformation belongs in code. If one reviewer catches the same failure repeatedly, perhaps that failure needs a test.

That is how more tools can eventually create less work.

The leverage is becoming cumulative

This is the part I find hardest to compare with the way I worked before Eterna. The biggest benefit is no longer simply that an AI can help me do something faster today. It is that today's work can reduce how much work the next version requires.

A provider helps solve a hard problem. Part of the solution becomes deterministic software. A process becomes a playbook. The next provider can retrieve the playbook. A failure becomes an evaluation. A useful pattern becomes part of EternaAI's training. The Workspace makes the resulting capability available again without requiring me to remember exactly which chat originally figured it out.

That changes the economics over time. The subscription may cost roughly the same next month, but the system using the subscription can be better.

I think that is the real opportunity for a solo founder now. It is not simply that AI lets one person type faster or produce more content. One person can assemble an unusually broad set of specialised capabilities, connect them to ordinary software, preserve what works and gradually turn repeated intelligence into operating infrastructure.

I still find new tools useful, and I still get excited when a provider releases something genuinely better. But I am becoming much less interested in finding the one system that does everything. The stack I already have is getting more useful every time Eterna learns how to use it better.

Every time I look at what is now running through that stack and then look at the monthly software bill, that is still the part I have trouble getting used to.

Inside the System Behind Eterna Clarity

Jesse Gamble — Fri, 25 Sep 2026 11:10:32 +0000

Four business lanes do not become one company just because they share a logo.

Xyterna. Business Health. Custom Systems. Adaptive Workspace.

Those are the visible parts of Eterna Clarity.

Underneath them is the system that helps the company operate as one company instead of four disconnected projects: the Eterna Engine / OS, Eterna AI, Knowledge, Control Center, Platform Manager, Sales & Acquisition, Networking, Studio and R&D / Lab.

The point is not to add complexity.

It is to keep company state, learning, priorities, distribution, relationships, creative work and experimentation connected as Eterna grows.

Every new product should not require rebuilding the company underneath it.

One company. Four business lanes. A connected system behind them.

https://www.eternaclarity.com/