What brought you to this point in RAGIC's history? And maybe tell us something that a lot of people don't know about you just for fun.

Okay.

One interesting fact, like a lot of even our friends at RADGIC doesn't know is that RADGIC is kind of the topic of my master's thesis.

So I wrote actually like conference and journal articles, paper, about this kind of thing.

new way to quickly build applications that can be semantically integrated with other database systems, you know, because it's an academic paper, so it has to have more academic components in it.

But in my master's defense, I actually built a prototype, a demo for it, which is like the oldest original version of Ragic.

So it's actually something that I worked on when I was a graduate student and when I was doing a lot of part-time work with big manufacturing companies in Taiwan.

But where else have you sort of seen these transformations taking place as we bring the business closer to the development process? What are some of the stories that you have with Ragic where you've seen maybe some transformational type results?

So

it's basically based on graph.

Like, because it came from semantic web, I was designing it as a graph.

So it has a lot more flexibility.

So you don't really need to change the data structure when you go from one to one to one to many or change it to many to many.

So that's one of the greatest strengths.

But it's just really hard to implement.

So I guess what I'll ask you is what went wrong that caused you to have to go down this path?

And then you can say, let's say in five years, wherever that is, 2031.

At least for me, at today's stage, in 2026, w- the smart way would be to leverage no code to do that.

Because with no code, you, you would be able to generate most of the, the scaffolds and the, the applications you need with AI to assist you with all these applications, and you, you will still be able to go in and tinker with all the setups and all the forms and reports that AI generated for you.

So at today's, yeah, 2026, that would be a pretty good combination so that, you know, you could AI generate the, the hard work for you, and you can go in there and look at it from a no-code tools perspective.

So there's not a lot of technical expertise needed when you're talking about, like, creating a CRM application or a business application like that with the assistance of tools like Ragic.

But if you're building something not business applications or, like, in other realms, I'm not sure.

But in your-- the, the case that you mentioned, I think that would be a pretty good combination.

Are those in parallel? Are they close? Does one outrun the other? Where do you think they land today? It depends, right? What kind of app i- is being built.