About Plasmatic

We build Orion.

Plasmatic is three people in three countries building runtimes that let business logic change without shipping a service. Orion is the one you can run today.

See what Orion does

Orion
dataflow-rs
datalogic-rs

All Apache 2.0. All public.See the source

Origin

Why we started

Between us we spent decades building systems that move messages between institutions. Different companies, different decades, the same pattern underneath.

A lot of what gets called a service is not doing computation. It parses a message, checks it against rules somebody wrote down, enriches it from another system, transforms it and sends it on. Necessary work, and not where anyone's advantage lies. That was tolerable when the rules moved slowly. They no longer do. Pricing, routing, thresholds and compliance logic all change faster than a release cycle can carry them, so changing a number means shipping a service.

Then generation got cheap, and the gap widened rather than closed. A team can now produce more services than it can review. The constraint moved from writing the thing to trusting it.

Plasmatic exists to separate the two. The rule is a document you can read, version, test and roll back. The runtime is something you install once, and it is where the guarantees live.

We built the first version for payment messaging, because that is the version of this problem with the least tolerance for being wrong, and because it is the world we came from. It is not a payments product. Payments is where the requirements were hardest.

The software is free. Our expertise is the service.

Worth being direct about this, because it determines how we behave and it is not going to change.

The platform is free and open, permanently.

Apache 2.0, self-hosted, no open-core edition, no paid tier holding the useful features. If Plasmatic disappeared tomorrow your Orion instance keeps running, your workflows are JSON you can read, and the source is public.

Bring us in when you need professional expertise.

Deployment into your environment, connectors to the systems Orion does not cover, and production hardening: observability, recovery paths, a runbook your team can operate.

Where the line sits.

Common, repeatable patterns ship into the open source repositories where everyone gets them. Work specific to your systems is what we charge for. If something you need looks like it belongs in the first category, tell us and it usually ends up there.

We turn work down.

If a piece of work is a genuine one-off with no reuse, we will say so and point you elsewhere. That is not modesty, it is the only way a team this size delivers anything properly.

Tell us which system

Founded by three people in three countries

Plasmatic is registered in Singapore. We work from India, Singapore and Australia, and we have never all been in the same room. That is a set of facts that should be doing real work in your assessment, so here is how we think it should.

The test we hold ourselves to is whether you still need us in month three.

Ask us something where the honest answer is bad for us

The risks, plainly. Capacity is limited. If two engagements land in the same month, one waits. We are inside the working day for most of Asia Pacific, but we are not a 24 hour rotation and we will not pretend to be. Three people carry continuity risk a large vendor does not.

Some of that is answered by structure rather than by a promise. The platform being Apache 2.0 and self-hosted is the exit path, and it is the same exit path whether you like us or not.

Some of it is genuinely better small. The people who build the platform are the people who do the deployment. There is no handoff from sales to delivery, because there is no sales team. When we say a connector is a week, that is an engineer's estimate rather than a proposal. And almost all of our work happens in writing, in public repositories, which began as a necessity of the time zones and turned out to suit an open source project rather well.

What to ask us for. A named scope with a defined end. A handover that includes a runbook. A straight answer on whether the thing you want is something we have built before, because the second time is much faster and you should know which one you are getting. And ask us what Orion is not for. Our documentation already answers that and it names Temporal, Kong and Drools.

The team

AKM Muthaalagan

Founder and CEO

Harishankar Narayanan

Founder, Engineering and Technology Strategy

Vinay Raja

Founder, Product and Experience

Work with us

The platform is yours. The delivery is what we do.

If you are evaluating Orion, start with the quickstart. It takes under a minute and does not require talking to us.

If there is a system you cannot see how to connect, or you want this live with a recovery path your team can operate at 3am, that is the conversation. Tell us which system and we will tell you straight whether it is a week or a quarter.

Tell us which system Run the quickstart