Sayonora

Warp

The Intelligent Database Gateway.

Accelerate, scale, secure, and observe Postgres, Oracle, MySQL, and SQL Server — in any cloud or on-prem.

Connect · Protect · Control · Accelerate · Observe

Oracle · MySQL · SQL Server · MongoDB · OpenSearch · DynamoDB · SQS · InfluxDB · GraphDB · PostgreSQL · gRPC · MCP

12 protocols. One execution pipeline.

One intelligent infrastructure layer for the database you already run.

Postgres, Oracle, MySQL, or SQL Server — same control point.

Why Warp?#

Put an intelligent control point in front of your database.#

Connect, protect, control, accelerate, observe — the same five things, applied identically no matter which protocol the caller speaks or which database sits behind Warp. Different protocols. Same policies. See each one broken out in detail →

What is Warp?#

See how Warp works, stage by stage → — the detailed eight-stage pipeline behind this diagram.

Two ways to use Warp#

See each outcome broken out in detail →

Four ways teams put Warp to work#

Explore all Warp capabilities →

Three products, two ways to use them#

Use Warp on its own to run the database you already have better, or bring in Ferry and Shim alongside it when you're ready to modernize onto Postgres.

Together: Ferry moves the data, Shim reduces the SQL and application changes, and Warp keeps existing clients and protocols working — all landing on the same Postgres.

Deploy anywhere#

Docker · Kubernetes · AWS · Azure · GCP · OCI · On-prem

Run Warp next to the applications and databases you already operate — no managed control plane required.

See it happen#

Pick a protocol — same demo, different client, same PostgreSQL on the other end.

$ sql app/password@//localhost:11521/postgres

SQLcl: Release 23.4 Production

SQL> SELECT * FROM orders;

ORDER_ID  CUSTOMER_ID  AMOUNT
--------  -----------  -------
    1001           42   129.99
    1002           57    89.50

2 rows selected.

SQL>

$ mysql -h 127.0.0.1 -P 13306 -u root -p

mysql> SELECT * FROM orders;

+----------+-------------+--------+
| order_id | customer_id | amount |
+----------+-------------+--------+
|     1001 |          42 | 129.99 |
|     1002 |          57 |  89.50 |
+----------+-------------+--------+
2 rows in set

mysql>

$ mongosh mongodb://localhost:27017

test> db.orders.find()

[
  { _id: 1001, customer_id: 42, amount: 129.99 },
  { _id: 1002, customer_id: 57, amount: 89.50 }
]

test>

$ curl -s localhost:9200/orders/_search

{
  "hits": {
    "total": { "value": 2 },
    "hits": [
      { "_source": { "order_id": 1001, "amount": 129.99 } },
      { "_source": { "order_id": 1002, "amount": 89.50 } }
    ]
  }
}

Real client. Real wire protocol. PostgreSQL database. No client rewrite. Table/document contents above are illustrative — the protocol and path are exactly real. (SQLcl, JDBC, and psql are what's most thoroughly verified today; see Warp capabilities for exact client-by-client coverage.)

Try Warp in 60 seconds#

What do you use? Point it at a Postgres you already have:

Different protocols. Same security policy.#

Oracle application? Same policy. MySQL application? Same policy. MCP agent? Same policy. Security follows the request, not the protocol.

SQL Firewall · ACL · Authentication · RLS · TLS · Secrets · Audit

Full, honestly-scoped security detail →

Stop one workload from taking down Postgres.#

QoS for Postgres, at the gateway. Prioritize, throttle, bound concurrency, and shed load — before Postgres saturates, not after it falls over. A real token-bucket admission controller, per workload class (query/write/ddl/txn). See Security for the full scope.

Cache once. Access across protocols.#

A result cached through one Warp protocol can be served through another — across Warp instances — without another Postgres round trip. One distributed cache, not a per-protocol silo. Confirmed live: a row read via a Postgres client, then asked for again through a MySQL client, comes back as a cache hit — zero Postgres round trips on the second read.

Cross-Protocol · Distributed · Automatically Invalidated · No Application Cache Code

Explore Mach — live terminal walkthroughs, DynamoDB/MongoDB point-lookup sharing, JOINs across wire protocols →

Explore Warp in depth — detailed architecture, comparison →

Built for enterprise Postgres#

Without Warp vs. with it#

Without Warp

• Different database infrastructure per protocol
• A separate connection proxy
• Different security controls per system
• Different observability per system
• Separate migration tooling
• A separate, unguarded AI access path

With Warp

One gateway → the database you already run, or Postgres.

• Fewer systems to operate — one gateway instead of five databases' own tooling.
• One place to govern workloads — the same firewall, QoS, and audit path for every protocol.
• Standardize on Postgres, or keep your current engine — without rewriting every application first, either way.

Warp vs. alternatives#

Capability	Direct to Postgres	Traditional proxy	Warp
Postgres wire protocol	✓	✓	✓
Foreign DB protocols (Oracle, MySQL, SQL Server, MongoDB…)	—	—	✓
Live dialect / semantic translation	—	—	✓, every call
SQL firewall	DB-side only	Some	✓
Workload QoS / admission control	DB-side only	Limited	✓
Intelligent routing	App/DB-side	Some	✓
Sharding	App/DB-side	Some	✓
Cross-protocol distributed caching	Separate system	—	✓
AI / MCP access, same governed path	Separate path	—	✓
Unified observability	Multiple layers	Proxy layer only	✓

Comparison methodology →

Compatibility, honestly scoped#

Every row below is verified against that protocol's real client library, not a synthetic harness — this table states only what's actually confirmed today.

Built for production#

• HA & FailoverMulti-AZ Warp deployment, planned drain/switchover and automatic unplanned failover, both tested across every wire protocol. See Multi-AZ deployment and Planned and unplanned outages.
• SecuritySQL firewall, connection ACL, authentication, TLS, row-level security identity propagation, Vault/CyberArk secrets, admin SSO. See Security for the exact, honestly-scoped detail.
• Workload protectionQoS admission control, connection pooling, and load shedding before a backend saturates — see "Stop one workload from taking down Postgres" above.
• ObservabilityPrometheus /metrics and OTLP export, reaching Grafana, Datadog, New Relic, CloudWatch, Azure Monitor, and GCP Cloud Monitoring. See Observability.
• DeploymentDocker, Kubernetes, AWS, Azure, GCP, OCI, or on-prem — your infrastructure, your network, your database.
• SupportCommunity support on Developer; enterprise support on Enterprise — see Pricing below.

Schedule a Warp Architecture Review →

Also from Sayonora

Ferry

Know before you migrate. Then move for real.

Explore Ferry →

Pricing

Same Warp, same protocols, same capabilities — Developer and Enterprise differ on scale and commercial rights, not features. Nothing that makes Warp what it is — SQL translation, the firewall, sharding, QoS, caching, HA/failover — is held back for a paid tier: an evaluation on Developer proves the exact architecture you'd run in production.

Sayonora Platform bundles Warp, Ferry, and Shim under one license at a discount to buying all three separately. Enterprise Unlimited is a company- or business-unit-wide agreement — unlimited deployments and migration environments across every product, negotiated directly. Starting prices above are exactly that — a starting point for the smallest real production footprint each product is sold against; talk to us for a quote on yours. Schedule a Warp Architecture Review →

Developer's connection/instance/backend limits are real, locally-enforced caps — not a time-limited trial and not a phone-home metering service. They're enough to run applications, demos, benchmarks, and a genuine three-instance HA/failover test; a meaningful production deployment will reach them quickly by design.

Ferry#

Assessment — connect, score, size, browse, report — is unrestricted on every tier. What's paid is the parts of actually moving the data that scale past a single-process, single-migration setup: real parallelism, unattended cutover, and multi-tenant capacity. Same WARP_LICENSE_KEY as Warp — one key, one thing to buy.

Full row-by-row capability breakdown, including exactly which real license check backs each row: Ferry capability table →

Shim#

Oracle/SQL Server/MySQL catalog and built-in-function compatibility inside Postgres itself — V$SESSION, DBMS_OUTPUT.PUT_LINE, sys.objects, GROUP_CONCAT — is what the Enterprise tier below unlocks. The same WARP_LICENSE_KEY that unlocks it also unlocks Warp and Sayonora DMS's own Enterprise tiers.

Full per-engine compatibility tables: Shim →

Common questions

• Does my application need to change to use Warp?No — your existing driver connects exactly as it always has, unaware Warp is on the other end. Learn more →
• Is Warp's sharding real, or just SQL text matching?Real — it decodes each protocol's own native bound values and merges cross-shard results centrally. Learn more →
• Does Warp support row-level security?Yes, for Postgres, SQL Server, and Oracle — a real per-caller identity feeds your own Postgres RLS policies. MySQL and the DynamoDB/MongoDB/SQS/OpenSearch wire protocols don't propagate identity into RLS yet. Learn more →
• What happens if the backend Postgres needs planned maintenance?A drain API redirects traffic and waits for a real zero-replication-lag cutover before confirming. Learn more →
• Can Warp connect to Supabase, RDS, Cloud SQL, Azure, or OCI?Yes — each has a worked example and its real provider-specific gotchas. Learn more →
• Does Warp cache query results?Yes — two tiers, both shared, neither a per-protocol silo. Arbitrary opted-in SELECT results: PostgreSQL, MySQL, Oracle, SQL Server, gRPC, and MCP all read the same cache. Exact primary-key point lookups (GetItem, find by _id, SQL WHERE pk = ?): DynamoDB and MongoDB each share that entry with any SQL client reading the same physical table too — see the demo above. Invalidation is automatic in both tiers. Learn more →
• Does Warp use AI for anything beyond MCP?Yes — ten features where Warp itself calls an LLM at a specific pipeline point: self-healing query repair on a real backend SQL error, natural-language firewall-rule drafting, traffic anomaly detection with plain-English narration, QoS tuning suggestions, MCP activity summarization, natural-language querying with a second LLM pass judging (and correcting) the drafted SQL, rollup pre-aggregation suggestions, table-sharding suggestions, EXPLAIN plan narration, and auto-generated schema documentation. Every one keeps the same split: a deterministic decision stays deterministic, the LLM only phrases, drafts, or judges, and nothing it produces is ever applied or executed without a check. See all ten →
• What security features does Warp actually have wired in?SQL firewall, connection ACL, QoS, authentication, TLS, secrets management, and admin auth — each scoped honestly. Learn more →
• Is Warp free to use?Yes — Developer is free forever with every protocol and feature enabled, capped on scale. See Pricing above.
• Is Ferry's migration score generated by an LLM?No — it's rules-based and reproducible: the same database gives the same score every time.

Contact

Considering Warp for production? Bring your architecture — we'll help map where Warp fits. Pick "Architecture Review" below.

Report an issue or ask a question — for either Warp or Ferry. Include what you were trying to do and, for a bug, what you expected vs. what happened. Goes straight to the team, no email address to copy or scrape.