The integrations already inside the Pwas ecosystem.

In projects using AI, the choice of model provider changes more often than anything else: prices change, performance on specific tasks changes, regulatory constraints change, and sometimes the organisation's position on where data may travel changes.

So the model is treated as a declared resource, replaceable per call, not as a library embedded in the application. Replacing it is a configuration change, not a rewrite of the automation, and different projects for the same client can use different providers depending on the sensitivity of the data they handle.

The same category includes the option of models hosted within a perimeter you control, which is the choice for anyone with strict confidentiality constraints who accepts the trade-off in model capability.

The runtime is containerised with no dependencies on one cloud provider's managed services. That means your usual infrastructure provider — or your own server room — is fine, and there's no list of supported clouds to check before starting.

It's a choice with a cost: we don't exploit the proprietary features that would make some things simpler on a specific platform. The benefit in exchange is that moving a project means moving containers and data, and that an infrastructure decision made today doesn't bind the ones you'll make in three years.

In projects where infrastructure is a hard requirement — public sector, healthcare, utilities — that property is worth more than any optimisation.

There's no marketplace of extensions to certify, and that's not an accident: in the declarative model an external service isn't a plugin, it's a declaration. Which calls it exposes, which fields it accepts, what it returns, what to do on error.

The practical consequence is that integrating a new tool requires neither our involvement nor a certification process: whoever builds the project declares it and it works. What's worth sharing are reusable declarations for widely used services — a carrier, a payment gateway, a public portal — that different partners meet in the same sectors.

If you have a technology you think fits the platform well, the useful conversation isn't about a formal agreement but about how it's declared and what it takes to make it work reliably.