Creem

What is Creem?

Creem is a Merchant of Record (MoR) that lets software companies sell globally without worrying about sales tax, VAT, compliance, or payment infrastructure. We act as the legal seller of your software, so you can focus on building.

What we handle for you:

• 🌍 Global tax compliance across 140+ countries (US state taxes, EU VAT, UK VAT, and more)
• 💳 Payment processing with optimized checkout experiences
• 🔄 Subscription management with trials, upgrades, downgrades, and dunning
• 💸 Automated payouts to your bank account
• 📊 Revenue analytics and reporting
• 🛡️ Fraud protection and chargeback handling
• 🏪 Storefronts for no-code product pages
• 🤝 Affiliate programs with built-in tracking and payouts

This repository contains Creem's maintained public SDK, CLI, integrations, UI packages, webhook types, examples, and documentation.

Packages

SDK and developer tools

Integrations

Checkout UI

Package documentation and installation instructions live in each linked package directory. The complete product and API documentation is at docs.creem.io.

Quick start

Install the recommended TypeScript SDK:

npm install creem

Create a checkout:

import { Creem } from "creem";

const creem = new Creem({
  apiKey: process.env.CREEM_API_KEY,
});

const checkout = await creem.checkouts.create({
  productId: "prod_123",
  successUrl: "https://yourapp.com/success",
});

console.log(checkout.checkoutUrl);

See the SDK README for resources, standalone functions, retries, error handling, and MCP setup. Framework users can start from the relevant integration or UI package above.

Repository structure

packages/
├── sdk/                       # creem; generated SDK + MCP binary
├── cli/                       # public CLI
├── core/                      # future shared primitive
├── webhook-types/             # temporary until absorbed into core
├── ingestion/                 # usage-event ingestion toolkit
├── integrations/
│   ├── better-auth/
│   ├── convex/
│   ├── nextjs/
│   ├── strapi/
│   └── framer/                # Framer plugin
├── ui/
│   ├── embed/
│   ├── react/
│   ├── svelte/
│   └── vue/
├── docs/                      # documentation application
├── examples/                  # standalone, workspace-excluded examples
├── templates/                 # future cloneable templates
└── creem-io/                  # frozen deprecated exception

Distribution

Creem publishes and deploys artifacts from this repository to the following destinations:

Each package README owns its exact build and delivery procedure. The root package-policy.json classifies packages for repository governance checks; it is not deployment configuration.

The README-only packages/creem-sdk, packages/better-auth, and packages/nextjs directories temporarily guide old repository backlinks to their new locations. Their review/removal is scheduled in OSS-51.

Filesystem paths and npm identities are deliberately independent. Moving a package into a category does not rename its published npm package.

Deprecated SDK

creem_io is frozen, excluded from normal CI and Changesets, and unsupported, including for security fixes. Do not use it for new projects. Migrate to the maintained creem package.

Development

Prerequisites

• Node.js 24 or newer
• pnpm 11 (use the exact version declared in package.json)

Setup and checks

git clone https://github.com/armitage-labs/creem.git
cd creem
pnpm install --frozen-lockfile

pnpm build
pnpm test
pnpm typecheck
pnpm lint
pnpm format:check

Filter to a package for local iteration:

pnpm --filter @creem_io/nextjs build
pnpm --filter @creem_io/nextjs typecheck
pnpm --filter @creem_io/nextjs test

The root CI workflow validates package policy, built tarball contents and entrypoints, build, typechecking, tests, lint, formatting, workflow paths, and plugin discovery. Changesets creates release pull requests and publishes eligible public packages with npm provenance after repository policy passes.

The creem SDK is generated from packages/sdk/openapi.json with Speakeasy. Do not hand-edit generated SDK source; see the contributing guide.

Contributing and community

Read CONTRIBUTING.md before opening a pull request. By participating, you agree to the Code of Conduct.

• GitHub issue forms for reproducible package bugs and documentation problems
• Discord for community discussion
• Featurebase for product feature requests
• SECURITY.md for private vulnerability reporting

License

This repository and its actively maintained public packages are licensed under the MIT License. The frozen deprecated SDK retains its historical license file.