The Thesis
Bad architecture is economic friction.
Every time a system loses energy to preventable technical drag, it reduces the capacity the organization has for real progress. Bad time models, fragmented coordination, and brittle integrations are not just engineering problems. They are economic ones.
Rheba is building the alternative: shared infrastructure where the underlying models are correct from the start. The date-time library is the first public layer. The availability engine and coordination API are next.
Build Surfaces
What developers can explore now and what is coming.
Date-Time Library
@rheba/time
The foundational time model. Encode, decode, format, and compute with RDate, RTime, and RNQH values. No epoch seconds, no timezone drift.
Explore →Availability Engine
Spatial-temporal availability
Query who is available, where they can be, and when — across groups, locations, and recurrence patterns. The core of the coordination layer.
Explore →Coordination API
Groups, identity, and scheduling
105 API endpoints for events, availability, groups, coordination requests, certifications, billing, and more.
Explore →Suite Applications
10 apps as reference implementations
Each app in the suite exercises parts of the SDK. They are working examples of what can be built on the shared architecture.
Explore →Internal Gears
Architecture as leverage, not just cleanliness.
Strong primitives, reliable abstractions, and stable infrastructure are not side conveniences. They are sovereignty assets. They make the system more capable of carrying its own weight. The SDK is how we open that up.