For growing support
Pro
Pooled usage for people and agents. The secure checkout confirms the current price and included allowance.
Built for people and agents
Your support starts here.
A shared workspace. Clear permissions. One place to get ready.
Checking your session…
Welcome to Daykeeper
A good place to begin.
Sign in securely with your identity provider. You can create your workspace in the next step.
Signing in does not create a workspace, activate an inbox, or start a paid subscription.
Your workspace
Give your support a home.
Signed in as .
Workspace creation is free. Connecting an inbox and enabling customer traffic are separate steps.
Workspace ownership verified
Signed in as .
- Workspace ID
Your support spaces
No support spaces yet. Prepare a website inbox below.
Preparation is separate from going live. Installation verification, identity setup, and traffic activation still need approval.
Send your first message
Create an “Issue customer sessions” key below and set it as DAYKEEPER_API_KEY in your backend environment. This Node.js example uses the management and customer SDKs.
For mobile, issue short-lived customer sessions from your authenticated backend. Never ship the API key to a client. This API inbox does not require a website widget or DNS setup.
New inbox preparation is not enabled on this console. Existing support spaces remain available to inspect.
Review your setup plan
The response was not confirmed. You can inspect your support spaces above or repeat the approved request with the same idempotency key. Do not start another setup to recover this request.
This queues an isolated support space and inbox within your current allowance. It does not enable customer traffic, email delivery, or billing.
Traffic limits and live status are not inferred from the workspace allowance.
Workspace-wide
Plan and billing
For higher volume
Scale
More pooled support usage with the same API and agent access. No fee per seat, API key, or MCP connection.
Starting checkout does not prove payment. Daykeeper changes the plan only after a signed billing event is applied.
Checkout is in progress
Complete the secure checkout, then return here and refresh. If its response was interrupted, recover only the exact original plan request.
You can inspect billing here. Checkout, portal, and budget changes require a verified human owner with separate billing approval.
Workspace-wide
Resource safety this month
Recorded across all support spaces in this workspace. These are safety counters, not invoice charges or proof that writes are currently allowed.
Workspace-wide
Agent access
Create a scoped credential for a local MCP client, CLI, or CI job. Hosted OAuth remains the preferred path for connected apps.
Shown once
Save now
Daykeeper cannot show this secret again. Store it in your password manager or secret vault before continuing.
Credentials
No credentials yet.
Older inactive credentials are omitted from this view. Current active credentials are always shown.
Let’s check that