SPECARIA SOAP-2-REST Product Overview

SPECARIA SOAP-2-REST is a no-code conversion platform designed to transform existing SOAP services into RESTful, OpenAPI-described endpoints (source: docs/customer/README.md). It automatically discovers services from gateway-edge traffic, deterministically maps them, and provides versioning and end-to-end observability (source: docs/customer/README.md). This product serves as an alternative to current API management platforms for API publishers with extensive SOAP backend estates who require REST modernization without a multi-quarter integration project (source: docs/customer/README.md).

Core Capabilities

The platform offers the following core capabilities (source: docs/customer/README.md):

• WSDL-driven automation: The system can fetch schemas and generate an OpenAPI v3 specification, producing a deterministic full-field mapping. This is achieved by uploading a WSDL or by allowing the system to learn services from gateway-edge syslog, eliminating the need to learn a proprietary mediation language.
• In-app observability: An Operations Dashboard, F5 Live Traffic Log, error-rate KPIs, top-error services, and per-VS failure breakdown are available. These features read from pre-computed aggregation tables, providing sub-second load times on tens of millions of rows.
• No-code administration: All onboarding, mapping review, publishing, and operational changes are performed through a browser UI accessible under the API publisher's tenant URL.
• Versioned, immutable mappings: Every modification creates a new revision, and rollback functionality is available with a single click.
• UTF-8 / locale-aware end-to-end: The platform supports UTF-8 and is locale-aware, including right-to-left scripts and gendered language.

How it Works

SPECARIA SOAP-2-REST operates by automating the conversion of SOAP services to REST endpoints (source: docs/customer/README.md). The process begins with either an API publisher uploading a Web Services Description Language (WSDL) file or the system learning services by analyzing gateway-edge syslog traffic (source: docs/customer/README.md). Once a WSDL is available, the platform fetches the necessary schemas and automatically generates an OpenAPI v3 specification (source: docs/customer/README.md). This generation includes a deterministic full-field mapping, ensuring consistency and predictability without requiring API publishers to learn a specialized mediation language (source: docs/customer/README.md).

All administrative tasks, such as onboarding new services, reviewing mappings, publishing endpoints, and making operational changes, are managed through a browser-based user interface (source: docs/customer/README.md). This no-code approach simplifies the management of the conversion process (source: docs/customer/README.md).

The platform maintains versioned and immutable mappings, meaning every change to a service mapping results in a new revision (source: docs/customer/README.md). This allows for easy rollback to previous configurations with a single click (source: docs/customer/README.md).

For operational oversight, the system provides in-app observability features (source: docs/customer/README.md). These include an Operations Dashboard, an F5 Live Traffic Log, key performance indicators (KPIs) for error rates, identification of top-error services, and a detailed breakdown of failures per Virtual Server (VS) (source: docs/customer/README.md). All these observability metrics are derived from pre-computed aggregation tables, ensuring rapid data retrieval even with large datasets (source: docs/customer/README.md). The system is also designed to be UTF-8 and locale-aware, supporting various scripts and linguistic nuances end-to-end (source: docs/customer/README.md).

Supported Installation Topologies (v1 GA Scope)

The v1 General Availability (GA) release targets common deployments for mainstream gateway products (source: docs/customer/README.md). Supported installation topologies include:

• GCP-native: Deployment using Cloud Run and Cloud SQL Postgres, facilitated by included PowerShell scripts.
• Kubernetes Helm chart: Compatible with any conformant Kubernetes cluster that has Postgres 15+ available.
• Marketplace listing: A one-click deployment option available from the GCP Marketplace.

Other topologies, such as OVA/VMware/Hyper-V/Nutanix images or AWS/Azure/Oracle ports, are planned for post-GA releases (source: docs/customer/README.md). For more details, refer to the "Choosing an install topology" section in install.md (source: docs/customer/README.md).

Support Model

The platform offers different support models (source: docs/customer/README.md):

• Community Edition: A free tier with a cap on the number of services. A license is automatically issued upon first boot, requiring no payment or commitment.
• Trial: A 45-day full-feature trial, automatically issued alongside the Community license on first boot.
• Enterprise: A paid tier offering unlimited services, vendor support, and a Service Level Agreement (SLA). Renewal tokens are uploaded via the Settings → License interface.

For the operator workflow related to licenses, see the "License Tab" section in daily-ops.md (source: docs/customer/README.md).

Where to Start

For specific usage and operational guidance, API publishers should refer to the following documentation (source: docs/customer/README.md):

If you're...	Read

---

All SOAP-to-REST docs