What is a tracking plan?

A tracking plan is a document that defines which analytics events your product tracks, what properties each event includes, and which platforms implement them. Ordaze replaces messy spreadsheets with a living, validated registry.

What is analytics event management?

Analytics event management is the process of defining, versioning, and governing the events your product sends to analytics platforms. It covers naming conventions, property schemas, ownership, and implementation coverage, ensuring every team ships consistent, trustworthy data.

Which languages do you support?

All 13 of Swift, Kotlin, TypeScript, Python, Java, JavaScript, C#, Go, Rust, Ruby, PHP, Dart, and React Native ship with default codegen templates. Each output matches the idioms and patterns native to that language and is fully customizable via Handlebars.

Can I use Ordaze with my existing analytics provider?

Yes. Ordaze works alongside Segment, Amplitude, Mixpanel, and any custom analytics setup. It generates the tracking calls, and your existing providers receive the data.

How does the CI/CD integration work?

Add our GitHub Action to your pipeline. It validates that your code matches the tracking plan schema on every pull request, catching mismatches before they reach production.

Is there a free plan?

Yes. The Free plan includes up to 100 events, unlimited team members, and full code generation. It's perfect for side projects and trying Ordaze before committing.

How does Ordaze help with data governance?

Ordaze centralises your event definitions and enforces them at the code level. Every event has an owner, a schema, and a version history. Breaking changes require a new version, creating an audit trail that satisfies data governance requirements.

What is event coverage scanning?

Coverage scanning analyses your codebase to check which events from your tracking plan are actually implemented, and which are missing or mismatched. The Ordaze scanner runs in CI or locally and reports results directly to your dashboard.

How does version control for tracking plans work in Ordaze?

You publish immutable versions of your event registry, just like software releases. Each version snapshots all event definitions and properties. Teams can compare versions, see what changed, and roll back if needed, giving product and engineering a shared source of truth.

Can multiple teams collaborate on a tracking plan?

Yes. Ordaze supports role-based access with Owner, Admin, Editor, and Viewer roles. Product managers can define event requirements, engineers can review and implement them, and analytics teams can audit coverage, all within the same workspace.

Does Ordaze support mobile analytics (iOS and Android)?

Yes. Ordaze generates native Swift files for iOS and Kotlin files for Android, with the same event definitions. The coverage scanner auto-detects your platform and scans the appropriate source files.

What analytics providers does Ordaze integrate with?

Ordaze is provider-agnostic: it generates the tracking calls and your existing provider (Segment, Amplitude, Mixpanel, Firebase, or custom) receives the data. There is no vendor lock-in.

How do I get started with Ordaze?

Sign in with Google at app.ordaze.com, create a workspace, and define your first events. Then publish a version, generate an API token, and run the scanner CLI in your repository. The quickstart guide walks you through each step in under 10 minutes.

What is type-safe analytics code generation?

Type-safe code generation produces tracking helper files (Swift enums, Kotlin data classes, TypeScript interfaces) directly from your event registry. Because the types are derived from the schema, the compiler catches mismatched property names or types before the code ships.

How does Ordaze handle breaking changes to events?

Adding or removing required properties is a breaking change. Ordaze flags these when you publish a new version and the CI scanner blocks merges that would violate the current schema, so downstream consumers always know what to expect.

Ordaze is built for product teams, engineering teams, and analytics teams that need to collaborate on analytics event tracking. It's especially useful for companies with multiple platforms (iOS, Android, web, backend) where inconsistent event naming creates data quality problems.

What counts as a tracked event?

A tracked event is any unique analytics event defined in your tracking plan. For example: ButtonClicked, PageViewed, or PurchaseCompleted. The limit applies to the total number of distinct event definitions, not to the number of times an event fires in production.

What happens when I hit the event limit?

You can still view and manage your existing events. Adding new event definitions will require upgrading to a higher plan. Your existing code generation and CI/CD integrations continue to work uninterrupted.

Can I switch plans at any time?

Yes. You can upgrade instantly and the new limits take effect immediately. Downgrades take effect at the end of your current billing cycle.

Is there a free trial for paid plans?

Yes. New signups get 14 days of full Pro access automatically, no credit card required. After the trial, you continue on the Free plan (1 workspace, unlimited members, 100 events) with no time limit unless you choose to upgrade.

Do I need a credit card to start?

No. The Free plan requires no credit card and has no time limit. You only enter payment details if you choose to upgrade to Pro or Team.

What happens to my data if I downgrade?

Your events and tracking plans are never deleted. If you exceed the lower plan's event limit, existing events stay intact but you will not be able to create new ones until you reduce usage or upgrade again.

Are there any long-term contracts?

No. Both Pro and Team are billed monthly with no annual commitment required. You can cancel at any time and your plan stays active through the end of the billing period.

Do you offer discounts for annual billing or nonprofits?

Annual billing and nonprofit discounts are not available yet, but both are on our roadmap. Contact us at hello@ordaze.com and we will notify you when they launch.

Ordaze is an analytics event registry for product and engineering teams. It gives you a versioned tracking plan, type-safe code generation for Swift, Kotlin, TypeScript, and Python, and a static source-code scanner that runs in CI to catch drift before it ships.

Does Ordaze work with Segment, Amplitude, Mixpanel, PostHog, and Firebase?

Yes. Ordaze is analytics-provider agnostic. The code generator ships default templates for Swift, Kotlin, TypeScript, and Python that you can shape around any SDK — Segment, Amplitude, Mixpanel, PostHog, Firebase, RudderStack, Snowplow, or a custom wrapper. The scanner detects analytics calls regardless of which SDK you use.

How does Ordaze detect breaking changes?

The scanner parses your source code, matches call sites against the published schema, and flags every mismatch: missing required properties, renamed events, deprecated events still in use, and type drift. In CI, the scanner fails the pull request when a breaking change appears, so the broken event never reaches production.

What is Ordaze?

Ordaze is an analytics event registry for product and engineering teams — a versioned tracking plan with type-safe code generation and a static source-code scanner that runs in CI.

TL;DR

Ordaze replaces spreadsheets and runtime validators with a single source of truth for your analytics events. You define events once, generate type-safe client code for Swift, Kotlin, TypeScript, and Python, and run a scanner in CI that fails pull requests when code drifts from the schema. Unlike runtime tools, nothing ships to production and no user data leaves your servers.

Who Ordaze is for

Product teams

Need a single source of truth for what every event means, who owns it, and which platforms implement it.

Ordaze gives them a versioned event registry with categories, descriptions, ownership, and lifecycle statuses (draft / active / deprecated).

Engineering teams

Need typed tracking calls so analytics mistakes are caught at build time, not in production.

Ordaze generates Swift, Kotlin, TypeScript, and Python wrappers from the schema. The compiler enforces required properties and catches rename drift.

Data / analytics teams

Need to know which events are actually firing, from which platforms, and when a release broke the tracking plan.

The Ordaze scanner reports coverage per platform and fails CI when code diverges from the published version.

How Ordaze works

1. Define events in the dashboard
Add events with snake_case names, typed properties, categories, and owners. Publish a version to snapshot the schema.
2. Generate type-safe client code
All 13 supported languages — Swift, Kotlin, TypeScript, Python, Java, JavaScript, C#, Go, Rust, Ruby, PHP, Dart, and React Native — ship with default Handlebars templates you can customize in the in-app editor.
3. Run the scanner in CI
npx @ordaze/scanner scan reports coverage and flags every mismatched or missing event. Wire it into GitHub Actions, GitLab CI, or any shell-based pipeline.
4. Block drift before it merges
The scanner fails the pull request when source code diverges from the published schema, so broken events never reach production.

Ordaze vs. the alternatives

Tool	Approach	Pricing	Where Ordaze fits
Ordaze	Source-code scanner + multi-language codegen. SDK-free, runs in CI.	Free / $29/mo / $79/mo flat, unlimited seats	—
Avo	Runtime Inspector + manual tracking plan, per-seat pricing, custom quotes.	Custom, seat-based	Ordaze is SDK-free and transparent on price; Avo is stronger on enterprise governance.
Amplitude Data	Branch-based plan with Ampli CLI that wraps Amplitude's own SDKs only.	Bundled with Amplitude Analytics (typically $60K+/yr)	Ordaze generates code for any SDK, not just Amplitude's; Amplitude Data is strongest if you're all-in on Amplitude.
Spreadsheet	Manual documentation with no compile-time or CI enforcement.	Free (time cost high)	Ordaze enforces the plan in code via codegen + CI; a spreadsheet drifts the moment code ships.

Want the full head-to-head? See all Ordaze comparisons.

When not to use Ordaze

You need runtime validation above all else

Ordaze scans source code statically — it catches drift before it merges, but it can't detect dynamic event names constructed from variables at runtime. If your priority is observing the live event stream, a runtime validator like Amplitude Observe or Trackingplan is a better fit.

You're all-in on a single analytics vendor

If your stack is 100% Amplitude and you want tracking-plan features inside the same UI, Amplitude Data's Ampli CLI will integrate more tightly. Ordaze is provider-agnostic, which is valuable for mixed stacks and nothing when you only have one provider.

You don't ship mobile or typed-language apps

The sharpest Ordaze value is in typed codegen + source scanning. If you ship a single server-side Python or Ruby service with no mobile or frontend, the scanner still helps but the codegen layer matters less.

FAQ

What exactly is Ordaze?

Ordaze is an analytics event registry for product and engineering teams. It stores your tracking plan as a versioned schema, generates type-safe client code for all 13 supported languages via default Handlebars templates, and ships a static source-code scanner that runs in CI to catch drift before it reaches production.

Does Ordaze replace my analytics provider?

No. Ordaze sits upstream of providers like Segment, Amplitude, Mixpanel, PostHog, and Firebase. The generated code calls your provider's SDK — Ordaze never receives your production event data.

Is Ordaze open source?

The Ordaze app is proprietary, but the scanner is open-source at @ordaze/scanner on npm and GitHub. The piece that touches your source code is fully auditable.

Does Ordaze need an SDK?

No. Ordaze is SDK-free. It reads your source code statically on any git branch. No third-party JavaScript runs on your site and no user data leaves your servers.

Which languages does Ordaze support?

Ordaze ships default Handlebars templates for all 13 supported languages: Swift, Kotlin, TypeScript, Python, Java, JavaScript, C#, Go, Rust, Ruby, PHP, Dart, and React Native. Every template is editable in the dashboard so you can match your SDK or house style.

How does the scanner work?

The scanner parses your source files, matches analytics call sites against the published schema, and reports coverage and mismatches. It runs as an npm CLI (npx @ordaze/scanner scan) or a GitHub Action, fails pull requests on breaking changes, and never ships to production.

How does pricing work?

Free forever with 100 events and 1 workspace. Pro at $29/mo flat adds 500 events and 5 workspaces. Team at $79/mo is unlimited events and workspaces. Every tier includes unlimited team members — no per-seat charges, no annual commitment.

Can Ordaze work alongside a runtime validator?

Yes. Ordaze catches drift at build time (in CI) and a runtime validator catches drift at ingest time (in production). They're complementary — Ordaze prevents the broken event from shipping, the runtime tool monitors for anything Ordaze's static analysis couldn't catch.

Who maintains Ordaze?

Ordaze is maintained by an indie team that ships weekly. The codegen layer, scanner, and CI integration all receive active development, and the changelog at /changelog lists every release.

How do I get started?

Sign up at app.ordaze.com with Google, define your first events, publish a version, and run npx @ordaze/scanner scan in your repo. The /docs/quickstart walkthrough takes about 10 minutes.

Try Ordaze on your own codebase in under 10 minutes.

Get started free Read the quickstart