The TCKC Factory
Applications produced in series — a workshop's care, a factory's cadence.
See the applicationsWhy a factory
Anyone can build an application. Operating several in parallel — regulatory assistants, a financial agent, a media outlet, a tradesperson's assistant — with a small team is another matter: every product wants its infrastructure, its content, its updates, its quality. TCKC's answer is industrial: everything that can be shared is shared, everything that can be automated is automated, and humans focus where they are irreplaceable.
What the Factory pools
A replicated base
One infrastructure mould per family: front-end, orchestration, retrieval — the same topology stamped product after product.
A product registry
Each product is described in a configuration; adding one is a production run, not a new project.
Shared services
Auth, payments, voice, emailing: wired once, served to all.
Content pipelines
Monitoring and publishing are automated — every article credits its source, substantive verification stays human.
Tooling agents
User feedback triaged into tickets, draft fixes, build and distribution chains driven by agents.
Replayable quality
Expert-question benchmarks and automatic verification passes, replayed at every change.
How a family is born
A family starts with a domain and a corpus — an accounting standard, a niche news beat, a catalogue of trade tasks. The Factory supplies the rest: the replicated technical base, the shared services, the pipelines. The result: the marginal cost of a new product shrinks to what makes it unique — its content, its guardrails, its promise.
- monassistant.pro: three regulatory assistants stamped from the same monorepo — accounting, labour law, taxes
- Braquage Six: a self-feeding outlet powered by automated monitoring, published statically, plugged into shared emailing
- iArtiBot: one identity and a task catalogue structured as trade prompts, ready to be declined season after season
The families today
FAQ
Is the Factory no-code?
No. It is careful, shared, replicated code: each product remains a real application with its own guardrails — the Factory industrialises production, not mediocrity.
What exactly is automated?
The replicated infrastructure, monitoring and publishing pipelines, build and distribution tooling, feedback triage. Editorial lines, domain guardrails and substantive verification stay human.
Why build several products rather than one?
Because every product enriches the factory: a shared service, a pipeline or a guardrail built for one immediately benefits the next. The more the Factory produces, the less each new product costs.
The Factory at work
Every application in the portfolio comes out of this base: regulatory assistants, a financial agent, a media outlet, a tradesperson's assistant.