Can you talk a little bit, Vince, about what Zafin built and what's running today and then share any other customer examples you want to weave in there as well?

Yeah, well, and I think Zafin actually is a great example of everything that I've talked about.

You know, they had exactly that case where customers would send huge amounts of data.

And, you know, what Zafin had done was gone down the path of, you know, custom ingestion per customer because of the differences from customer A to customer B and, you know, so on and so on.

You know, I think that the ultimate issue they got into with that is just the processing time got to be, you know, relatively enormous there.

And it was a brittle kind of situation.

You know, the customer could change something and all of a sudden, you know, Zavin might not even know it.

How does Propels help the mainframe team who's already got these tens of extract programs and a line out the door?

So I

mean, just to cover propels from a high level for anyone who might not be familiar with the core technology.

Propels is really just an open-ended replication platform.

At the core is a series of things like data filtering and transformations and so on and so on.

We know how to take complicated binary objects, let's say a record from a VSAM file, and we know how to transform that into a lot of different things.

It could be a JSON object, an XML object, but certainly the most common thing would be a format that can be inserted directly into some type of database.

Database could be on-prem, it could be in the cloud, doesn't really matter too much to us.

So, you know, we we we talked about

Maybe, Vince, you can talk us through those three approaches.

Yeah, well, and just to build on your example, I think the customer you're referencing had actually been through all of these three.

So it certainly hit home to them.

I mean, something we see a lot of folks do is they'll go down the path of ETL, extract, transform, and load.

And the idea there is that, you know, you have to know the structure of your data and you do something, you know, you use, you know, utility from one of our competitors, maybe you write custom COBOL programs, you know, whatever you want to do, you create, you know, data dependent scripts that can transform your data into something useful.

And of course, the problem with that is that it's very brittle.

Every time your data changes, your scripts have to change.

Why don't you talk a little bit about what the actual setup was and how we accomplish this?