Tulsk is joining riggd.ai

Today we're announcing that Tulsk is becoming part of riggd.ai — a new company we're starting whose mission is to bring AI Harness to Asian SMEs.

If you use Tulsk, the short version is this: nothing about your experience changes today. Same product, same pricing, same login, same team. We're writing this so you hear it from us first, and so you know what we're building toward.

The change, in one paragraph

Tulsk will continue to exist as a product. The legal entity it sits under is changing. The team is the same — Kevin and Max are still here, still shipping. The Tulsk you sign into next Monday is the Tulsk you signed into last Friday. Over time, we expect Tulsk's enterprise features to ship faster as part of this move, not slower.

What riggd.ai is

riggd.ai is an AI Forward Development company. The thesis is simple: most Asian SMEs know they should be adopting AI, but they don't have a path to actually do it. They have process gaps, integration gaps, and skills gaps. They don't need another chatbot — they need a working AI system wired into the parts of the business that actually move.

We use the term AI Harness for that working system. AI Harness is Tulsk's engine — EMA, the agent runtime (Hermes, OpenClaw, and more to come), and Skills — packaged so a 30-person manufacturer in Taipei or a 50-person logistics firm in Bangkok can plug it into their workflows in days, not quarters.

This isn't a pivot. It's a delivery vehicle for what Tulsk already does.

Why we're doing this

Building Tulsk taught us that the bottleneck for AI adoption in real businesses isn't model quality. It's three things, in order:

Where the agent lives. AI in a chat window dies the moment you close the tab. AI in a shared workspace — on a project board, in a comment thread — can actually carry the job.
Who teaches it the company. No SME has time to hand-roll skills, runtime, auth, and integrations. The "wiring" is the cost.
Who owns the verdict. Someone has to decide whether the work the agent did is good enough. That role doesn't exist on most org charts yet.

Tulsk already solves the first one and partly the second. riggd.ai is the company that goes the rest of the way for SMEs: pre-wired clusters, industry-specific skills, and a delivery model that doesn't require the customer to hire an AI team first.

What "AI Harness" actually is

When we say AI Harness, we mean a specific stack:

EMA as the orchestrator — owns plans, memory, and the verdict on whether work was done well
Agent runtime as the worker layer — Hermes Agent today, OpenClaw alongside it, others later; each agent gets a browser, shell, file system
Skills as the institutional knowledge — markdown files that teach agents how this specific company runs

Today, a Tulsk Team plan customer wires this up themselves. Under riggd.ai, an SME gets it as a deliverable: configured, integrated, and trained on their own playbook. Same engine. Different delivery.

What this means for you, if you use Tulsk today

Four things, in order of likely concern:

Your account, your data, your billing — unchanged. Same URL, same login, same plan, same invoice.
The team building the product — unchanged. Kevin on product, Max on engineering, same roadmap conversations, same release cadence.
The pace of Tulsk shipping — likely faster. Being part of a company that ships AI Harness into real SMEs every week tightens our feedback loop. Enterprise pain points become Tulsk features.
Brand and domain — may change later, but never silently. If at some point Tulsk's URL or brand moves under riggd.ai, we'll give you advance notice and a migration path. You will hear it from us before you read it anywhere else.

"Isn't this just you going enterprise and forgetting builders?"

It's the obvious objection, and it deserves a real answer.

We started Tulsk for the founder who is stuck because nobody is moving the work but them. That reader is still our reader. The free EMA plan, the cluster of six, the focus on momentum over chat — none of that changes.

What changes is that the same engine we built for that founder now also runs inside 50-person SMEs trying to adopt AI without standing up a 5-person AI team. The economics of that — bigger contracts, real production load, harder integration problems — make Tulsk a sturdier, faster product for everyone, builders included.

If we ever start to drift, you'll see it in the changelog before you see it in the marketing.

What to do next

If you're a current Tulsk user: keep going. Nothing on your end needs to happen.

If you're an Asian SME wondering how to adopt AI without burning a year on integration: see Tulsk pricing or wait a few weeks for the riggd.ai launch. We'll link to it from here when it goes live.

If you're reading this as a fellow builder: we'd rather you ship in Tulsk than read about us. Try EMA free →

— Kevin Ong & Max Li Co-founders, Tulsk