HyperQuery™ Resources FAQ

FAQ

Answers to the most common questions about HyperQuery™ and ASTRO™.

What is ASTRO™ and how is it different from an LLM?

ASTRO™ (Autonomic SQL Transformation and Query Rewrite Optimization) is HyperQuery™ patent-pending, purpose-built SQL inference engine. Unlike general-purpose LLMs, ASTRO™ is 100% SQL-aware, 100% self-contained (no outside LLM calls), and applies relational algebra and relational calculus to produce mathematically proven, deterministic rewrites. LLMs guess — ASTRO™ proves.

Why am I charged $199 even if the rewrite looks similar?

ASTRO™ charges only when a genuine optimization is identified. If no optimization is found, there is no charge. The $199 reflects the value of a mathematically verified, production-safe PerfectSQL™ rewrite — not just a reformatting. Even subtle changes can deliver 100X or greater performance gains.

Do I need to provide a schema or make database changes?

No. ASTRO™ requires no schema, no database changes, no application changes, and no additional hardware. It optimizes SQL in isolation, purely from the query text itself, making it safe and simple to deploy anywhere.

Which SQL dialects are supported?

HyperQuery™ supports 17 major SQL dialects: ANSI, BigQuery, ClickHouse, Databricks, DuckDB, Hive, MySQL, Oracle, PostgreSQL, Presto, Amazon Redshift, Snowflake, Apache Spark SQL, SQLite, StarRocks, Trino, and SQL Server (T-SQL). Any-to-any rewriting is supported in any combination.

How do I know the rewrite is correct?

Every PerfectSQL™ rewrite produced by ASTRO™ is semantics-preserving and verifiable by mathematical proof. The rewrite report shows exactly which rules fired, how many iterations the fixpoint loop ran, and the structural diff between the original and optimized query.

Is my SQL data stored or used for training?

No. Queries are processed in-memory and discarded after the rewrite response is delivered. We do not store, log, or use query content for any training, analytics, or data-sharing purposes. Your SQL is yours.