RUO ProA DSCO product

Developers

Build on Flightdeck.

Flightdeck is the commerce platform behind RUO Pro — one API for products, checkout, and site content, with a typed SDK on npm, a live API reference, and open-source starters you can deploy today.

The platform

This is Flightdeck.

RUO Pro runs on Flightdeck — dsco's commerce platform. One backend serves both a hosted storefront and anything you build headless with the SDK. The docs, the API reference, and every package you install are Flightdeck.

A faceted crystal refracting violet light — the Flightdeck identity

Install

Start with the SDK.

The client is typed end-to-end from the OpenAPI spec. A non-2xx surfaces as a typed error — a failed read is never a silent empty result.

npm install @dscodotco/sdk
import { createStorefrontClient } from "@dscodotco/sdk";

const client = createStorefrontClient({
  apiUrl: "https://api.ruo.pro",
  tenant: "your-tenant",
  storefrontToken: process.env.STOREFRONT_TOKEN,
});

const { products } = await client.products.list();

const order = await client.checkout.submit(body, {
  idempotencyKey: crypto.randomUUID(),
});

Open source

Four packages, MIT-licensed.

@dscodotco/sdk

Fully-typed client for the commerce API. Every path, param, and response checked at compile time.

npm install @dscodotco/sdk
View on npm

@dscodotco/theme-presets

Combinable storefront themes — palette, typography, and structure composed into design-system tokens.

npm install @dscodotco/theme-presets
View on npm

@dscodotco/compliance-gates

CI gates for ADA/a11y, ARL auto-renewal, CCPA, Prop 65, CAN-SPAM, and dark-pattern consent.

npm install @dscodotco/compliance-gates
View on npm

@dscodotco/storefront-sections

The storefront section library — heroes, product grids, content blocks — as composable React components.

npm install @dscodotco/storefront-sections
View on npm

More on how we build in the open: Open source

How it fits

One API, two frontends.

The same API powers the hosted storefronts and anything you build yourself — the demo store runs both ways. Sections, navigation, and theme authored in the merchant studio are available headless via store.site.get(), so a custom frontend renders exactly what the merchant configured, without a redeploy.

Community

Build something on it.

We want developers on this platform. Questions, proposals, and bug reports run through the starter repo — that is where the team works.

Full documentation is live at docs.ruopro.com.

Ready to
build?

Research Use Only, not for human consumption.