Cybernetks: 2026

I've been working as a freelance consultant for over ten years, mostly on larger web development projects that I could really sink my teeth into.

Over that time, the role of a consultant has changed. Where deep specialisation once sufficed, today we’re expected to be far more well-rounded across stacks, tools, and disciplines. That’s a challenge I enjoy, but it also comes with a tension: experimentation doesn’t always fit neatly into client work.

Last year, I started a new branch alongside my consultancy: Cybernetks.

Cybernetks is a solo studio where I build games, tools, and software that entertain, empower, and solve real problems. It exists to give me room to explore new technologies, build my own products, and experiment. Without putting that risk on client projects.

As a father of three, time and energy are limited resources. After a full day of work and family life, there isn’t much left to burn on ambitious side projects. That reality forced me to rethink how I approach this studio.

Instead of chasing speed or scale, I set a long-term goal.

The 2026 Goal

Self-sustaining doesn’t mean replacing my income or quitting consultancy. It means something much simpler and more realistic:

Cybernetks should be able to exist, operate, and grow without needing my personal money or constant attention.

What "Self-Sustaining" Means

Cybernetks is self-sustaining when:

• It pays for all of its own operational costs (hosting, domains, tools, services)
• Its projects justify their existence through use, learning, or revenue
• It does not require constant attention to survive
• It fits within my life without eroding family, health, or motivation

This definition allows the studio to move slowly, honestly, and sustainably without turning into another source of pressure.

Start-Up Costs & Project Rules

New projects still need a starting point. Domains, hosting, and tooling don’t appear out of thin air, so some start-up costs are explicitly allowed:

• Domains
• Initial hosting
• App store fees
• First months of infrastructure
• Tools needed to reach a first usable version

These are intentional investments, not failures of sustainability.

After launch, every project must eventually do at least one of the following:

• Pay for itself
• Serve real users
• Feed back into the Cybernetks ecosystem through skills, assets, or tooling

Projects that do none of these are paused or sunset. Letting things end is part of keeping the studio healthy.

Building in Public (Carefully)

Cybernetks is built in public, which is easily the most uncomfortable part for me.

Because life is busy and unpredictable, I don’t follow a fixed content schedule. I share work when something is finished or when I’ve learned something meaningful. This is about clarity and continuity, not algorithms or audience growth.

You’ll see posts here, in the newsletter, and on social platforms with:

• Experiment updates
• Project progress
• Lessons learned
• Thoughts on building and development

I’m also experimenting with Twitch and YouTube. Streams focus on build sessions, devlogs, and occasional co-working. Videos are a way to turn written updates into another format for those who prefer watching over reading.

No hype. No pressure. Just honest work, shared as it happens.

Catch you in the next log!