Problem
Calendar math gets messy as soon as the clock matters.
A simple due-date calculation can become a support bug when it crosses Friday afternoon, a weekend, a Monday holiday, business-hour windows, or timezone boundaries. A shared API keeps deadline answers consistent across tools.
When to use it
- You need support, logistics, legal, or admin deadlines with business-hour SLA rules.
- You need a due timestamp that skips closed hours, weekends, and US federal holidays.
- You need one repeatable deadline calculation before wiring the logic into another tool.
- You need repeatable US federal holiday-aware due dates across tools.
- You want to avoid copying deadline logic into every workflow.
Non-goals
- Not a full workforce-scheduling or shift-planning system.
- Not international holiday coverage beyond the calendars the API exposes.
- Not a ticket, logistics, or CRM product by itself.