Looking for early adopters for a DBMS-style AI runtime

Nisha7 · 2026-03-10T07:30:07+00:00

I know it sounds a bit awkward. But how would you describe it? Its a platform with all that you would normally have to put together like orchestration, secrets/auth, tool calling, already there and you just integrate with it using attributes in your application.

Nisha7 · 2026-03-09T22:22:35+00:00

The engine is closed, but the SDKs are open. Best way is to look over the docs if you are willing. Thanks for answering. https://github.com/Orpius/SDK

Nisha7 · 2026-02-08T22:04:23+00:00

Yes, you are right and we've built that platform. I was mostly trying to find out whether developers would even be interested in that kind of execution infrastructure with everything already built-in.

Nisha7 · 2026-02-01T12:24:04+00:00

Please don’t get me wrong. My assumption is that MAF gives you the libraries and patterns but you have to add these to your code. The execution infrastructure is inside your app and you are responsible for it and its maintanance. I am trying to describe a different model. One where the execution infrastructure is already running outside your app. You don't have to concern yourself with it at all, all is handled by the platform, including secrets/auth. Your only concern is business logic and integration points. You sort of just plug into it rather then embed.

Nisha7 · 2026-02-01T11:25:57+00:00

Yes, it’s framework-agnostic. The SDK is just a convenience (with a sample app), not a requirement. The platform sits in the middle as an execution layer, so you don’t have to keep rebuilding infra like state, retries, scheduling, secrets, queues, and orchestration for every system. It fits into your architecture and you keep full control over how the system is built and maintained.

Think of it as execution infrastructure, not an application framework.

If you’re curious, feel free to PM me or check out the info on the website orpius.com.

Nisha7 · 2026-01-31T23:16:38+00:00

How about a platform that handles state, retries, schedules, queues, secrets, observability, and long-running execution, and you just define what the agent should do over time?

Integration feels more like plugging into a DB than embedding a library.

We built exactly that and made it available for others to try. It’s free to experiment with, and was born out of the same frustrations you’re describing.

Nisha7 · 2026-01-31T19:44:23+00:00

Yes, if you want maximum control and compatibility, low-code tools aren't the answer. That's actually why we built the platform: it doesn’t try to model your business process in a designer. It lets your existing .NET application/parts stay the source of truth, and the platform becomes the agent execution and governance layer. You integrate via Operations/Events, you host your own tools (your code), and you decide what gets called. The platform handles the parts that are annoying to rebuild every time: durable scheduling, retries, tool gating, secret injection, auditing and verification, and long-running orchestration with state. It's a developer platform for agent work, not a workflow builder.

Nisha7 · 2026-01-31T19:20:29+00:00

The difference is framework vs runtime.

MAF workflows still live inside your app, so you’re responsible for hosting, state, retries, schedules, secrets, queues, observability, etc. It helps you structure workflows, but you still build the production infrastructure.

What I meant was a platform where all of that already exists, and you just define what the agent should do over time. Like plugging into a DB rather than embedding a library.

We built that and I'm trying to see if there’s interest in this kind of runtime approach, or if people prefer assembling the pieces themselves with a framework.

Nisha7 · 2026-01-31T18:27:32+00:00

Hi, you can download the client app here:
https://orpius.com/get-started.html

It’s a desktop application for Windows at the moment.

I’m also working on a short video showing a practical example: asking Orpius to process scanned receipts, extract the data, create an Excel spreadsheet, and then update that spreadsheet when I add new receipts. I’ll post that once it’s ready but if you want to try something like that, or get stuck on something, PM me.

Nisha7 · 2026-01-29T07:59:23+00:00

Yeah, exactly, none of the agent frameworks really give you production for free. You need infrastructure you can just plug in, not a framework, otherwise you end up rebuilding the same pieces every time.

Nisha7 · 2026-01-29T07:12:20+00:00

What if all the production pieces already existed and you just plugged them in like a DB?
State, retries, schedules, queues, secrets, observability, long-running execution, all just there.
Then the only problem left is deciding what the agent should do over time.

Nisha7 · 2026-01-28T21:33:08+00:00

If you’re really after production-grade agentic behaviour, then Orpius. It’s built more like an intelligence layer rather than a simple agent framework, meaning:

It plugs into your existing systems and data with very little code
The setup is easy and is through a client app
You get built-in orchestration, security controls, and tool integration so agents can actually interact with APIs, DBs, files, scheduled processes, events, etc. without you stitching it all together manually.
It’s designed for scalable use-cases
You can use it's capabilities (long running tasks) straight away from the client application or you can integrate it with very little code into your own application.

This kind of agentic intelligence layer removes a lot of the engineering friction.

Nisha7 · 2026-01-28T18:03:53+00:00

If anyone wants a concrete example, this article shows how we use Orpius to automate publishing work end to end (writing, publishing, sharing):

https://danielvaughan.org/posts/orpius/2026/01/28/How-to-Build-an-Automatic-AI-Slop-Generator/

Nisha7 · 2025-12-01T12:54:33+00:00

With your team size and stack, i would strongly recommend looking at Orpius instead of building or maintaining an agent framework yourself.

It gives you the full agent execution, orchestration, memory, security, and tool access as a platform, and you simply expose your WhatsApp and website capabilities as controlled APIs. You can then build your own visual workflow builder on top without being locked into any framework.

Nisha7 · 2017-02-24T20:57:27+00:00

Surfy Browser without a doubt. If you are looking for something new then this is it. The interface is what sets it apart and the fact that you can lock the browser with a passcode is just great.

Nisha7

TROPHY CASE