API modernization

Specaria SOAP to REST

Modernize your SOAP estate. Without rewriting it.

Expose a live SOAP estate as REST + OpenAPI v3 inside your own VPC — auto-discovered from gateway-edge traffic, deterministically mapped, and observable on day one. No service rewrites, no proprietary transformation language, no data leaving your infrastructure.

GA · todayGCP · Helm · Docker Compose · GCP MarketplaceRequest a SOAP to REST license

What it does

9 capabilities you’ll actually use.

No marketing checklist. Every capability below ships in the preview build.

# openapi.yaml — generated from accounts.wsdl openapi: 3.1.0 info: title: Accounts version: v3 paths: /accounts/{id}: get: operationId: getAccount parameters: - in: path name: id required: true responses: "200": description: "OK"

Auto-discover services

No WSDL hunting. Listen to gateway-edge traffic; SOAP services materialize in the console with 24-hour, 7-day, and 1-month volumes.

Deterministic full-field mapping

Generated from each WSDL/XSD. Every element, attribute, and optional field covered — no transformation language, no hand-coded mediation.

OpenAPI v3 per service

One standards-compliant contract per service. Importable into developer portals, SDK generators, and AI-agent toolchains.

Real production payloads

Live request/response payloads captured from traffic and curated as learned examples — not synthetic placeholders.

In-app observability

Per-call traffic, latency, errors, SLO reports, dashboards, audit. One surface, no external analytics SKU.

Versioned, immutable mappings

Every change is a new revision; rollback is a click. Activations, role bindings, and config changes are signed and audited.

14 gateway and load-balancer connectors

F5, NetScaler, HAProxy, nginx, Kemp, A10, Radware, DataPower, Layer7, webMethods, Akana, Mashery, Oracle OAG, plus a generic-HTTP receiver.

UTF-8 and locale-aware

Hebrew, Arabic, and other RTL scripts handled end-to-end. Gendered Hebrew, per-tenant timezone, normalized regex patterns.

Pluggable IdP

Google IAP, Azure AD, SAML, OIDC. RBAC mapped from IdP groups — admin, operator, reader.

How it works

5 steps. End-to-end, in one product.

Discover

The platform listens to your gateway-edge traffic and auto-discovers the SOAP services running in production — no WSDL hunting, no service-catalog upload.

Map

For each service it generates a deterministic, full-field SOAP↔REST mapping from the WSDL — every element, attribute, and optional field covered by default.

Publish

A standards-compliant OpenAPI v3 contract is generated per service, importable into developer-portal tools, SDK generators, and AI-agent toolchains.

Capture

Real production request/response payloads are captured from live traffic and curated as learned examples, so consumers see what actually flows.

Observe

Per-call traffic, latency, errors, dashboards, and audit surface on a single in-app observability stack — no separate analytics product.

Connectors & integrations

14 connectors. Plus a universal HTTP on-ramp.

Plug into the gateway edge your SOAP traffic already flows through. Discovery enumerates inventory through each vendor’s management API; ingest receives the traffic logs that drive discovery, learned examples, and observability.

Load balancers

Vendor	Discovery	Ingest
F5 BIG-IP	Edge config + sample iRule for client-IP injection	Syslog via relay
Citrix NetScaler / ADC	NITRO REST API	Syslog
HAProxy	Data Plane API (Enterprise) / stats socket (OSS)	Access-log feed
nginx	Config parsing (OSS) / management API (Plus)	Access-log feed
Kemp LoadMaster	REST API	Access logs
A10 Thunder ADC	REST API	Syslog
Radware Alteon	REST API	Syslog

API gateways

Vendor	Discovery	Ingest
IBM DataPower	REST management interface	HTTP log target
CA / Broadcom Layer7	Restman API	Transaction log feed
Software AG / IBM webMethods	Mediator + Gateway REST APIs	Transaction logs
Perforce Akana	Akana Platform API	Analytics feed
TIBCO Mashery	Mashery API	Analytics feed
Oracle API Gateway (OAG)	Management console	Log export

Generic

Vendor	Discovery	Ingest
Generic-HTTP receiver	—	Documented JSON envelope from any gateway, app server, or appliance that can emit HTTP traffic logs

What’s in the box

4 containers. Scale them independently.

The control plane and the data plane ship as separate images so you can size them for your traffic, not ours.

`s2r-runtime`	Conversion engine. Terminates REST, forwards SOAP. Stateless, autoscaling with a warm minimum instance.
`s2r-admin-api`	WSDL import, mapping CRUD, version activate / rollback, observability endpoints.
`s2r-admin-ui`	No-code browser console. Onboarding wizard, dashboards, live traffic log, audit views.
`s2r-worker`	WSDL parsing, code/model/spec generation, alert evaluation, synthetic monitoring.

Who buys this

5 kinds of organization.

Integration architects who want a deterministic, contract-first way to expose SOAP as REST without writing mediation logic per service.
Platform-engineering leads who need one platform that runs in their VPC, scales to ~1M calls/day, and is operable by a small team.
Engineering managers looking for a faster, cheaper path to modernization than rewriting services or buying a heavyweight integration suite.
Procurement teams who want transparent pricing, a 45-day full-feature trial, and a free community tier — no sales call required to see the price.
API-consuming teams (mobile, partners, AI) who want clean REST + OpenAPI v3 with real example payloads, ready to import into their toolchains.

Performance & scale

A tested baseline, not aspirational numbers.

Engineered for a real enterprise traffic baseline and proven against it with repeatable load tests that can be re-run against your environment before you go live.

~1M calls/day · ~12 rps sustained · ~100 rps burst

Scenario	Profile	What it proves
Sustained	~12 rps for an extended window	The ~1M-calls/day baseline holds with p95 latency and error-rate within budget.
Burst	~100 rps for ~60 seconds	Peak-stress tolerance with no server errors.
Slow backend	Sustained load against a deliberately slow backend	Timeouts and retries stay bounded; the platform degrades gracefully.
Dashboard read path	Sub-second across hundreds of discovered services	Pre-computed aggregation tables — the firehose is never scanned at query time.

Security & data sovereignty

The entry ticket for regulated workloads.

Built to clear the bar by default — data residency, network exposure, access control, secrets, accountability, and traceability are first-principles, not add-ons.

Runs in your VPC — traffic, payloads, archives, learned examples, and the metadata database stay in your infrastructure.
No public endpoint — internal-only networking by default; access mediated by your internal load balancer and identity-aware proxy.
RBAC with three roles — admin, operator, reader — mapped from IdP groups, direct in-app bindings, or an emergency bootstrap list.
Pluggable identity at GA — Google IAP, Azure AD, and standard SAML / OIDC; Okta, Keycloak, and custom SAML profiles on the roadmap.
Backend credentials encrypted at rest, never returned in API responses, never written to logs.
Complete audit trail — every configuration change recorded with actor, action, before/after state, and a correlation ID end-to-end.

Languages & localization

UTF-8 is preserved end-to-end — REST payloads, SOAP envelopes, the metadata database, generated OpenAPI, and the admin UI. Hebrew and Arabic render correctly RTL, gendered Hebrew is handled, and date/time fields respect a per-tenant timezone.

Use cases

4 scenarios. Where the product earns its place.

Expose a SOAP estate to mobile and web apps

Customer- or citizen-facing apps need REST + JSON; the systems of record speak SOAP. Discover the SOAP services from live traffic, generate a deterministic full-field REST mapping and OpenAPI v3 per service, and serve REST consumers — without touching the SOAP backends.

Open a partner / B2B integration surface

Partners want a documented, standards-based API, not a WSDL and a SOAP toolkit. Publish OpenAPI v3 with the response shape, error format (including RFC 7807), and field casing your partners expect — all configurable, all reflected in the generated contract.

Enable AI agents and LLM toolchains

AI agents reason over JSON and import OpenAPI tools — they cannot consume a SOAP estate directly. Every discovered service becomes a JSON/REST tool with a standards-compliant OpenAPI v3 description and real-payload examples captured from production.

Build a live inventory of a forgotten SOAP estate

Nobody has a current list of which SOAP services are running, who calls them, or how often. Traffic-driven discovery builds a ranked inventory from live gateway traffic — every service with 24-hour / 7-day / 1-month volumes and consumer attribution.

License tiers

Preview free. Lift the cap when it matters.

Community and Trial licenses are auto-issued the first time the runtime boots. Enterprise licenses are reviewed by a human, usually within two business days.

Tier	Cap	Term	Vendor support
Community	Capped services	Indefinite	Community
Trial	Unlimited	45 days, auto-issued	Community
Enterprise	Bundled services, with overage	Annual	Basic included; advanced add-on

Request a SOAP to REST license.

Install the preview today. Issue a license when the caps start to bite.

Request a SOAP to REST license All products

Loading…