Skip to main content
Orient

API platform toolkit · 7 integrated products

Build API platforms with Orient

Orient is a cohesive toolkit for designing, securing, configuring, and operating modern API platforms — from contract-first specs to observability and dispatch. The name reflects orientation: where you are, what changed, and what to do next.

Scroll to the ecosystem overview

Ecosystem

One platform vocabulary for API teams

Orient products share metadata, validation, and deployment patterns so you spend less time gluing tools together.

Composable modules

Adopt one product or the full stack. Shared contracts keep services consistent without a monolith.

Spec-to-ship workflow

Start from OpenAPI, validate changes early, and propagate policies through deployment pipelines.

Operator-friendly

Configuration, security, and observability primitives are designed for platform teams and service owners alike.

Products

Metadata-driven product catalog

Every card is rendered from src/config/products.ts. Add or update entries there — the layout, validation, and tests follow automatically.

Available
SpecPulse
API monitoring and contract drift

Tracks live APIs, records contract changes, and keeps Swagger/OpenAPI documents in sync with what production actually serves.

  • Scheduled health probes and sync jobs
  • Contract change history
  • Worker + web console (WFE)
Available
Pipelink
Lightweight CQRS mediator for .NET 10

MediatR-inspired request/response and notifications with pipeline behaviors, assembly scanning, and native streaming—MIT-licensed and tuned for minimal overhead.

  • Request, notification, and stream patterns
  • Scoped-safe handler resolution
  • NuGet 2.x on .NET 10
Available
anyscan
Architecture and quality gates for .NET

Part of the Any() toolkit: continuous architecture, security, performance, and configuration analysis via CLI, CI, MCP in Cursor, and optional Hangfire/GitHub automation.

  • ARCH / SEC / PERF / CONF rule packs
  • surface · standard · deep scan depths
  • JSON, SARIF, and MCP tooling
Available
Paramio
On-prem hierarchical configuration

AWS Parameter Store–style platform for project and environment parameters: Draft → Publish → Rollback, RBAC, audit logging, and a .NET IConfiguration provider with ETag polling.

  • PostgreSQL-backed parameter store
  • Next.js admin console
  • Paramio.Extensions.Configuration SDK
Available
Dispatcher
Fair PR reviewer assignment

PR Reviewer Dispatcher (pr-bot): multi-tenant Go worker that assigns reviewers on GitHub or Bitbucket, posts Microsoft Teams Adaptive Cards, handles reminders, digests, and write-back to the provider.

  • Availability- and workload-aware strategies
  • Priority tags, draft handling, quiet hours
  • Next.js admin UI · Postgres store
Coming soon
Shield
Defense in depth for APIs

Apply policy templates for authentication boundaries, rate limits, and request hardening across the mesh.

  • Policy packs
  • Gateway integration points
  • Threat-aware defaults
Coming soon
Lens
See every request path

Correlate traces, metrics, and structured logs for distributed APIs without bolting on another dashboard silo.

  • OpenTelemetry alignment
  • SLO-oriented views
  • Trace-to-log correlation

Product lifecycle

Orientation by status

A compass-style view of the catalog—pick a maturity label and see which products share it.

Orient is about orientation—knowing where each tool stands. Turn the dial by choosing a status; icons settle on the compass arc. Labels are independent, not a mandatory path.

Platform

Designed for long-lived API estates

Orient favors explicit contracts, auditable configuration, and operability over one-off scripts.

Contract governance
Keep OpenAPI sources authoritative and gate merges on compatibility checks.
Policy as configuration
Encode rate limits, auth boundaries, and routing rules as versioned configuration — not scattered middleware.
Observable by default
Align traces and structured logs with the same identifiers your specs and handlers already emit.
Progressive adoption
Ship SpecPulse today, add Paramio next quarter, and layer Shield when policies mature — no rip-and-replace.

Workflow

From contract to production path

An opinionated but optional flow teams can adopt incrementally.

01

Model

Author or import OpenAPI. SpecPulse validates structure and compatibility.

02

Configure

Bind Paramio profiles and run anyscan in CI before changes merge.

03

Protect

Apply Shield policies at the edge when your platform is ready for production traffic.

04

Operate

Assign reviewers with Dispatcher, track contracts in SpecPulse, and scan with anyscan before merge.

Get in touch

Tell us what you are building or modernizing

One message is enough to start. Share your API platform context and which Orient products you care about—we reply with a concrete next step, not a generic deck.

Contact address not configured on this deployment.