Skip to main content

Platform

The Amazon data platform
you actually own.

Managed SP-API and Advertising pipelines land directly in your Postgres and S3. From there, every BI tool or AI agent works on the same source of truth — without paying us for read access. See integrations

Sources in. Warehouse out.

One managed pipeline turns the Amazon API surface area into clean, versioned tables in the database you already control.

  1. Sources: Amazon APIs

    • Selling Partner API (orders, inventory, settlements, FBA)
    • Advertising API (Sponsored Products, Brands, Display)
    • Brand Analytics & Search Query Performance
  2. DataBrill Core Pipeline

    Managed extraction & modeling

    • Token rotation, retries, and backoff handled for you
    • Schema versioning when Amazon changes a field
    • Historical backfill plus continuous incremental syncs
    • Normalized tables, idempotent loads
    • Per-workspace isolation
  3. Destinations: Your warehouse

    • Postgres (managed by us, or bring your own)
    • S3 / object storage for raw report archives
    • Direct connections from Looker Studio, Power BI, Metabase, and any BI tool that speaks Postgres

Three layers, one platform.

Pipeline

The brittle part of an Amazon data project — report jobs, retries, schema changes — solved once, by us.

  • OAuth onboarding for SP-API and Ads
  • Region-aware extraction across NA, EU, FE
  • Granular per-report scheduling
  • Monitoring and alerts when Amazon misbehaves

Warehouse

The database your finance, ops, and BI teams treat as the source of truth.

  • Clean, queryable Postgres schemas
  • Stable column names and forward-compatible migrations
  • Raw S3 archive for re-derivation and audit
  • Bring-your-own-database option at every tier

Agent-ready surface

A real schema is the difference between a useful AI agent and a polite hallucination.

  • SQL-callable views for LLM tool use
  • MCP-style metadata for Claude, Cursor, and your own agents
  • Per-workspace credentials
  • No vendor lock-in — point any agent at the warehouse

What lands in your database.

Every table is documented, idempotent, and stable across schema versions.

Orders & settlements
Orders, items, refunds, FBA fees, settlement reports.
Inventory & FBA
FBA inventory, inbound shipments, reserved units, age and storage fee snapshots.
Advertising
Sponsored Products, Brands, Display campaigns, ad groups, keywords, placements.
Brand Analytics & SQP
Search query and catalog performance, top search terms, repeat purchase, market basket. Coverage depends on account and report eligibility.
Catalog
Listings, attributes, variations, BSR, pricing history, buy box snapshots.
Reimbursements
Lost-and-damaged events with the supporting line items, ready to file.
Vendor reports (roadmap)
Vendor Central support is on our roadmap.
Raw archiveS3 / object storage
Every report we ever pulled, stored in your S3 bucket, replayable on demand.

Inside the schema

Two representative Postgres views with selected key columns. Examples of the documented schema, rather than live customer data or a complete table list.

amazon_orders_by_day_and_sku
local_date_first · merchant_id · marketplace_id · sku · asin · total_price
amazon_ads_campaign
merchant_id · marketplace_id · campaign_id · name · state · ad_product

Platform FAQ

Questions, answered.

Do I need a data engineer to use the platform?
No. We handle ingestion, modeling, and schema versioning end-to-end. You point any tool that speaks Postgres at the warehouse and start querying. A data engineer can help you work faster, but is not required.
What happens when Amazon changes a field?
Schema versioning. We add the new column without breaking the old one, document the change, and forward-fill where Amazon makes that possible. Migrations are forward-compatible — your queries don't break overnight.
Can I run my own SQL transformations on top?
Yes. The schema is yours — write views, materialized views, dbt models, whatever. We don't mind. We only own the raw + lightly modeled layer; the marts are yours.
How do you handle multi-region accounts (NA / EU / FE)?
SP-API data has a separate pipeline per region, because of how Amazon built that API; Advertising API data does not. Depending on the table, rows are identified by merchant ID, country ID, marketplace ID or a combination, and some primary keys include currency.
Is there an API to read the warehouse?
The warehouse is the API. Postgres credentials or MCP for AI agents — pick whichever fits the consumer. We don't gate the data behind a separate billed API surface.

See the schema.
Then own it.

Get started with your own warehouse, or book a walkthrough. See integrations