How to Retrieve ParadeDB Pricing in PostgreSQL

Galaxy Glossary

How do I query ParadeDB pricing directly from PostgreSQL?

parade_pricing() returns ParadeDB SaaS price tiers directly from SQL.

Welcome to the Galaxy, Guardian!
You'll be receiving a confirmation email

Follow us on twitter :)

Oops! Something went wrong while submitting the form.

Description

Example H2

Example H3

What does parade_pricing() do?

The function parade_pricing() ships with the ParadeDB extension and exposes ParadeDB’s public price list as a queryable table. Use it to surface cost details inside dashboards, alerts, or automated cost-calculation jobs without leaving SQL.

When should I query pricing from SQL?

Embed live pricing in admin portals, join price data to product margins, or trigger alerts when ParadeDB costs approach budget limits. Pulling the data from the database avoids brittle API calls in application code.

How do I install the function?

Install the ParadeDB extension once per database: CREATE EXTENSION IF NOT EXISTS paradedb;. The parade_pricing() function becomes available automatically.

Which parameters can I pass?

Specify currency, billing_cycle, and plan_name to narrow results. Omit a parameter to get all prices. Each argument is optional and defaults to NULL, meaning “no filter.”

Can I join pricing to ecommerce tables?

Yes. Because parade_pricing() returns a record set, you can JOIN it to Orders, Customers, or Products. This enables margin calculations, cost rollups, or UI displays that combine internal and ParadeDB data.

Best practices for live pricing queries

Cache pricing for 5–15 minutes in a materialized view to avoid repeated network calls. Index on columns you filter by most (e.g., plan_name) for faster lookups. Always select only needed columns.

Common mistakes to avoid

Calling parade_pricing() inside large loops causes unnecessary network traffic; instead, query once and reuse the result. Forgetting to set the correct currency leads to mismatched numbers in international dashboards.

Why How to Retrieve ParadeDB Pricing in PostgreSQL is important

How to Retrieve ParadeDB Pricing in PostgreSQL Example Usage


-- Join ParadeDB pricing to product costs
SELECT p.plan_name,
       pr.name        AS product_name,
       pr.price       AS product_price,
       pp.unit_price  AS paradedb_price,
       (pr.price - pp.unit_price) AS margin
FROM parade_pricing('USD', 'monthly') pp
JOIN Products pr ON pr.id = 42
WHERE pp.plan_name = 'team';

How to Retrieve ParadeDB Pricing in PostgreSQL Syntax


SELECT *
FROM parade_pricing(
    currency TEXT DEFAULT 'USD',      -- e.g. 'USD', 'EUR'
    billing_cycle TEXT DEFAULT 'monthly', -- 'monthly' or 'annual'
    plan_name TEXT DEFAULT NULL       -- 'free', 'team', 'enterprise'
);

-- Example with filters
SELECT *
FROM parade_pricing('USD', 'annual', 'team');

Common Mistakes

Running parade_pricing() on every page load. This makes an external call for each request and slows down the app. Fix by caching results in a materialized view and refreshing every few minutes.
Filtering without matching case (e.g., 'Team' vs 'team'). The function expects lowercase values. Wrap filters in LOWER() or use the correct lowercase literals.