Linear, Backlog, and Jira can tell you what your team should be doing. They can't tell you whether the team has time to do it. OneSlate /team is the calendar layer underneath — capacity-aware sprint planning, smart assignment, burnout signals — wired into the tools you already use.
Every two weeks, engineering managers look at a backlog, a team, and a calendar. They estimate, they assign, they commit. By Wednesday of week one, the plan is wrong. By Friday, no one mentions the plan anymore. The reason is simple: the plan never accounted for the calendar.
None of these belong in a spreadsheet. All of them are calendar-shaped problems. We just turned them into API calls.
40 hours per person per week is a fairy tale. After standups, 1:1s, recurring meetings, vacation, and that all-hands you forgot about — your real capacity is 50–65% of nominal. OneSlate tells you the actual number, per person, per sprint, in one API call.
"Round-robin" and "WIP limits" assume everyone has equivalent free time. They don't. OneSlate looks at who's actually free in the window the work needs to happen — and suggests assignees by real availability, not by ticket count.
If someone's calendar load + assigned story points has exceeded their personal threshold for three weeks running, OneSlate quietly flags it. To them, to their manager, to nobody else. The thing every "people analytics" vendor promised but never delivered.
Each of these is a documented API recipe. None of them require leaving Linear or Slack. Linear OAuth and /team availability are live today — Slack notifications and smart-assignment automation ship next.
At sprint start, hit /team/capacity. Get back the real number — meetings deducted, vacation deducted, recurring commitments deducted. The Excel sheet your EM maintains every two weeks, deleted.
New Linear issue, Priority: High, due Friday. Hit /team/suggest-assignee with the constraints. Get back the engineer who actually has the time — not just the lowest WIP count. Stop assigning to the wrong person.
Every morning at 9:00, a Slack message lands in your team channel. Who's heads-down today, who's in meetings all day, who's blocked. The standup question "what are you working on" answers itself.
An issue gets a due date. OneSlate predicts whether it'll actually land — based on the assignee's real upcoming calendar density, their velocity, and the issue's estimate. The deadline either fits the calendar or it doesn't. We tell you which.
For four weeks running, if (meeting hours + assigned story points × hours/point) exceeds the person's threshold, OneSlate sends a private signal — first to them, then to their manager. The "I had no idea" excuse, eliminated.
OneSlate /team subscribes to your Linear webhooks, queries the relevant calendars, and posts back through Slack — or back into Linear itself as comments.
If you want raw API access, the same data flows through api.oneslate.tech/v1/team/* — three endpoints, JSON in / JSON out, no SDK required.
See it live: hit /api/v1/demo/availability (no key required) — JSON in your browser in 200ms.
// Linear → OneSlate → enriched response // Posted automatically when an issue is assigned { "event": "Issue.assigned", "issue": { "id": "ENG-1247", "title": "Migrate auth to Clerk", "assignee": "tanaka@company.com", "estimate": 8, "due_date": "2026-05-11" }, "oneslate_check": { "assignee_capacity_remaining": "4.2 hrs", "calendar_density_next_5d": "82%", "realistic_eta": "2026-05-14", "verdict": "3_days_late", "suggested_alternates": [ { "user": "kim@", "capacity": "14.0 hrs" } ] }, "action": "slack_dm_sent_to_em" }
OneSlate /team uses the same three-tier pricing as the rest of OneSlate's API. No per-seat traps. No "contact sales for a quote." Read tier is free; Linear integration starts at the Write tier.
Once Linear integration ships. Today, you can lock in your key.
Email + workspace domain. Instant. No card. We email you the moment Write API ships.
OAuth Linear, OAuth Google Workspace or Microsoft 365. We map team members to calendars automatically.
Sprint capacity? Smart assignment? Burnout warnings? Toggle the ones you want. They post into Slack or your Linear comments.
I'm building OneSlate solo right now. That means I'd rather tell you the truth than ship a half-working integration and call it GA. Here's the public roadmap:
The deal: sign up now, you keep Early Access pricing forever. When Write API ships, you get 90 days free before billing starts. If anything breaks, email me directly — onojun@oneslate.tech — and I'll fix it the same day.
API keys issued instantly. Free during Early Access. The first 100 sign-ups get a direct line to the founder when their integration goes live.
Get your API key →