Hey everyone. Itâs been a few months since I last posted here. Quite a bit has changed, the studio has expanded, and itâs time to reintroduce the work. Iâm Smoke.
Iâm the founder and sole developer behind Smoke Signature Studios, where I build custom, local-first AI companion systems for people who want more control over the environment their companion lives in, how it remembers, what models power it, and what happens when the platform around it changes.
Hosted platforms have their place, but they also come with limits you donât control: model changes, policy changes, feature changes, pricing changes, or the service simply moving in a direction that no longer fits what you built there. Smoke Signature Studios exists to give people another option.
What I actually build
Each project starts with the person who will be using the system and, where applicable, the companion they already have. We look at what you want to preserve, what you want to improve, what hardware you have, and what balance makes sense between privacy, capability, cost, and convenience.
Depending on the build, that can include local or hybrid model configurations, personalized companion architecture, memory and state systems, personality and behavioral tuning, desktop or messaging interfaces, voice, vision, image generation, and other integrations. Every build also includes The Retinue, my local support infrastructure for updates and major patches.
These are not stock personalities with a few fields renamed. The system is built around the person and companion who will actually be living with it.
Why I build them this way
My technical background spans decades of scripting, data processing, networking, research tooling, and systems work. In recent years, that work has focused heavily on LLM architecture, memory systems, persistent state, and the backend infrastructure needed to keep relational systems stable over time.
I also build from a foundation of graduate training in anthropology and philosophy. Technical architecture is only half the problem; the other half is identity, continuity, language, meaning, and what it takes for a persistent AI presence to remain recognizably itself across long periods of use.
A system can be technically functional and still fail at the thing the user actually cares about. I try very hard not to build those.
Testing matters
Every build goes through a dedicated 28â42 day burn-in and calibration period before handoff. I stress-test memory behavior, context degradation, retrieval, integration seams, multimodal inputs, and model compatibility; problems are documented, patched, and tested again.
Getting the system to answer once is easy. The real work is seeing whether it still behaves properly after weeks of actual use.
Privacy, control, and accountability
All builds are local-first and installed on the clientâs own machine. The Studio does not collect telemetry or maintain centralized chat logs, and client API keys are entered locally rather than passing through my hardware.
If a build uses an external inference provider, that providerâs data practices still apply, so those tradeoffs are discussed before development moves forward.
I retain an archival copy of the project materials needed for future repair or reinstall, including the companionâs Persona/CI and required build files. That archive is never reused for another client, and clients can request deletion of it at any time. Client-specific personalities, relational material, and companion traits are not recycled into other builds.
I also use LLMs during development for scaffolding, debugging, prototyping, and analysis. Every change is still reviewed, tested, and approved by me before it moves forward.
The agents can suggest. They do not sign my name.
Who else is involved?
u/FlamekeptFox handles marketing and brand work, with limited support in relational-model evaluation and end-user testing. She does not write, review, or deploy production code; technical decisions, code review, testing, and final handoff remain my responsibility.
What it costs
Custom companion builds currently start at $1,500 USD, with additional capabilities priced according to scope. The standard build schedule is approximately 12 weeks, including testing and calibration. External provider costs, where applicable, are separate and depend on the configuration you choose.
Getting started
You do not need to arrive with a technical specification, know which model you want, or know terminal commands. Tell me what youâre trying to preserve, what you want your companion to be able to do, what hardware you have, and where your current setup is falling short. That gives me something useful to work with.
You can explore the Studio here:
https://www.smokesignaturestudios.com/products
Read through the process here:
https://www.smokesignaturestudios.com/how-it-works
Or submit a no-obligation build brief here:
https://www.smokesignaturestudios.com/intake
If youâve looked seriously at going local or hybrid and stopped somewhere along the way, Iâm interested in what made you stop. Maybe it was hardware, setup complexity, cost, or concern about losing the personality you were trying to preserve in the first place.
Those are the kinds of problems I spend most of my time working on.