Boundary is a monorepo of 24 libraries publishable to Clojars, plus developer tooling. Every library follows the same FC/IS structure, making the codebase instantly familiar across libraries.
| Library | Purpose |
|---|---|
Foundation: validation framework, case/type conversion utilities, interceptor pipeline, feature flags. No shell layer — entirely pure functions. | |
Cross-cutting observability: structured logging, metrics, tracing breadcrumbs, and pluggable error reporters (Datadog, Sentry). | |
HTTP routing/interceptors, database integration, CLI/runtime wiring. Infrastructure for feature libraries. | |
Shared UI contract: centralized CSS/JS bundles, tokens, and reusable style conventions across libraries. | |
Internationalisation: marker-based translation, locale chain resolution, EDN catalogues, Ring middleware, and Babashka tooling. |
| Library | Purpose |
|---|---|
Authentication, authorization, MFA (TOTP), session management, JWT tokens. | |
Auto-generated CRUD admin UI from schema. Hiccup + HTMX, no frontend build step. | |
File storage: local filesystem and AWS S3 / S3-compatible backends. | |
Interactive module code generator. Generates FC/IS modules with tests and migrations. | |
Distributed caching with TTL, atomic operations, and multi-tenant isolation. Redis and in-memory backends. | |
Background job processing with priority queues, retries, exponential backoff, multi-tenant support. | |
Email sending: SMTP, async, and queued via jobs integration. | |
Multi-tenancy with PostgreSQL schema-per-tenant isolation. Requires PostgreSQL. | |
WebSocket real-time communication, JWT auth, topic-based pub/sub. |
| Library | Purpose |
|---|---|
External service adapters: Twilio SMS/WhatsApp, SMTP/IMAP. | |
Payment provider abstraction: Stripe, Mollie, and Mock adapters with checkout-session flow and webhook verification. | |
Declarative state machine workflows with permission-based transitions and audit trail. | |
Full-text search: PostgreSQL FTS with LIKE fallback for H2/SQLite. | |
PDF, Excel (XLSX), and Word (DOCX) generation via | |
Recurring events, RRULE recurrence (DST-aware), iCal export/import, conflict detection. | |
Geocoding (OSM/Google/Mapbox), DB-backed cache, rate limiting, Haversine distance. | |
Rule-based audience segmentation: | |
Mobile push notifications via FCM and APNs: | |
Framework-aware AI tooling: NL scaffolding, error explainer, test generator, SQL copilot, docs wizard. |
These libraries are not published to Clojars — they are part of the monorepo and available automatically.
| Library | Purpose |
|---|---|
Dev-only: error pipeline (BND codes), dev dashboard (localhost:9999), REPL power tools, guidance engine, request recording, AI REPL commands. | |
Dev-only: deploy to Clojars, config doctor, setup wizard, scaffolder integration, quality checks, i18n management. |
All libraries share the org.boundary-app group:
{org.boundary-app/boundary-core {:mvn/version "1.0.1-alpha-26"}
org.boundary-app/boundary-user {:mvn/version "1.0.1-alpha-26"}
org.boundary-app/boundary-admin {:mvn/version "1.0.1-alpha-26"}
org.boundary-app/boundary-platform {:mvn/version "1.0.1-alpha-26"}
;; etc.
}Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |