Skip to main content

What makes Kreya a good SoapUI alternative

SoapUI, created by Smartbear, has been around for ages. It was one of the earliest GUI programs for testing APIs and mainly focused on SOAP (hence the name). A while ago, Smartbear released ReadyAPI as the commercial (and very expensive) alternative to the free SoapUI. ReadyAPI isn't covered in this comparison.

Here is why Kreya is a good SoapUI alternative and why you should consider switching from SoapUI to Kreya.

Kreya vs SoapUI comparison: What are the differences?


Feature / topicSoapUIKreya
Modern UI
gRPC support
REST support
SOAP support
Environments and templating
Directory settings
Reusing authentication()
Directory settings
Storing data locally
Free plan

Modern tooling

SoapUI still runs on Java 1.8 and it shows. The UI looks and fells like every outdated Java application. The usage of Java 1.8 also hinders the usage of modern protocols. For example, SoapUI does not support HTTP/2.

It also shows the mindset of Smartbear that SoapUI is no longer a priority, as that has shifted to the commercial ReadyAPI version. Feature requests, such as importing OpenAPI 3, are ignored for years and probably will never be implemented.

No gRPC support

Users looking to test gRPC APIs with SoapUI will be disappointed. SoapUI does not support gRPC, only REST and SOAP. SOAP usage is in decline, while gRPC is rising in popularity.

Environments and templating

Switching between different environments is a core feature of most popular API testing clients. However, SoapUI does not support this feature. This makes testing different environments of the same API (for example Test and Production) difficult.

Kreya does support environments. In combination with the powerful templating language Scriban, this makes switching between testing different environments very easy.


Kreya supports several authentication mechanisms such as OAuth2 or Windows authentication, which SoapUI also supports. Reusing the same authentication configuration in Kreya is easy, as there is no need to duplicate authentication information for different requests. Comparing this with SoapUI, it is much more of a hassle to reuse the same authentication configuration for multiple requests, as the authentication parameters must be copied each time.

Directory settings

A feature that makes Kreya a joy to use are the directory settings. It allows users to specify default settings for multiple operations in a folder or the whole project. For example, if all operations in a project use the same host or the same authentication configuration, it only needs to be specified once. This even supports templating and environment specific values, so switching between environments works flawlessly after the initial configuration. SoapUI does not have a comparable feature.