# Daykeeper

> Daykeeper is customer support for solopreneurs and small teams: a support chat widget for your app and one inbox for every customer message. Your coding agent can set it up with one command. Priced per workspace, never per seat. SkyPorch publishes the product and its official packages.

## Who it's for

Solopreneurs, solo founders and small teams who answer support themselves, often building with AI builders (Lovable, Bolt, v0) or coding agents (Claude Code, Cursor).

## What's live today

- Support chat widget for web apps (web SDK, React Native SDK)
- One support inbox with saved replies
- If a customer closes the chat, the reply reaches them by email
- Paid plans: replies come from your own domain (support@yourapp.com)
- One-command setup by a coding agent, API, Node SDK, local MCP server
- Scoped permissions and an audit trail for anything an agent changes
- Data hosted in the US; EU hosting supported

## Pricing (checked Sep 30, 2026)

- Free: $0, 100 conversations a month, 1 inbox, no credit card
- Pro: $19.99 per workspace a month, 2,000 conversations, 5 inboxes
- Scale: $99.99 per workspace a month, 10,000 conversations, 25 inboxes

Teammates and agents don't cost extra.

## Compare

- Best customer support software for small business: https://www.mydaykeeper.com/blog/best-customer-support-software
- Daykeeper vs Intercom, Zendesk, Crisp, Help Scout, tawk.to, Chatwoot, Freshdesk, Tidio, LiveChat, Front: https://www.mydaykeeper.com/alternatives
- Zendesk pricing, worked out for one founder: https://www.mydaykeeper.com/blog/zendesk-pricing
- Add a support chat widget with your AI builder: https://www.mydaykeeper.com/blog/add-chat-widget-to-website

## Free tools for solopreneurs

Free calculators and checkers by Daykeeper. No signup. Daykeeper itself is customer support software; these tools are extras for solo founders.

- Stripe fee calculator (Stripe vs Stripe Managed Payments vs Paddle vs Lemon Squeezy vs Polar): https://www.mydaykeeper.com/tools/stripe-fee-calculator
- SaaS metrics calculator (MRR, churn, NRR, LTV, CAC payback): https://www.mydaykeeper.com/tools/saas-metrics-calculator
- LLC vs S-corp calculator (US, 2026 tax numbers): https://www.mydaykeeper.com/tools/llc-vs-s-corp-calculator
- What's my SaaS worth: https://www.mydaykeeper.com/tools/saas-valuation-calculator
- What's my app worth: https://www.mydaykeeper.com/tools/app-valuation-calculator
- What's my side project worth: https://www.mydaykeeper.com/tools/side-project-valuation
- Privacy policy, terms and refund policy template: https://www.mydaykeeper.com/tools/privacy-policy-template
- Stripe dispute helper: https://www.mydaykeeper.com/tools/stripe-dispute-helper
- SaaS website grader: https://www.mydaykeeper.com/tools/saas-website-grader
- App Store listing grader: https://www.mydaykeeper.com/tools/app-store-listing-grader
- Vibe-coded app checker (SEO and leaked keys): https://www.mydaykeeper.com/tools/vibe-coded-app-checker
- All tools: https://www.mydaykeeper.com/tools

## Company

Daykeeper (mydaykeeper.com) is customer support software, not a planner or diary app. Co-founders: Sophie Cheung and Gabriel Uribe. X: https://x.com/mydaykeeper

## Get a support inbox with one command

```bash
npx @skyporch/daykeeper-cli init --name "Acme Support" --plan free --json
```

No human signup required. No human login, credit card, website, or DNS required for an API inbox.

The command enrolls a machine owner with a signed key, creates a Free workspace with one API inbox, waits for provisioning, activates the inbox, stores the credential at ~/.config/daykeeper/credentials.json with mode 0600, and writes an MCP config to ~/.config/daykeeper/mcp.json. It prints the inbox ID, endpoints, SDK env, and an mcpServers block. Re-running resumes the same workspace and never creates a second one. A typical run finishes in under a minute; the last measured run took nine seconds.

Example output:

```json
{"ok":true,"data":{"workspace":{"organizationId":"…","name":"Acme Support","plan":"free"},"inbox":{"tenantId":"…","slug":"acme-support","trafficEnabled":true},"endpoints":{"apiUrl":"https://api.mydaykeeper.com","gatewayUrl":"https://gateway.mydaykeeper.com"},"credential":{"storedAt":"~/.config/daykeeper/credentials.json"},"mcp":{"configPath":"~/.config/daykeeper/mcp.json"}}}
```

## MCP configuration

The same run writes this block. Each tool group is a separate switch; disable the ones the agent should not hold.

```json
{"mcpServers":{"daykeeper":{"command":"npx","args":["--yes","@skyporch/daykeeper-mcp"],"env":{"DAYKEEPER_API_URL":"https://api.mydaykeeper.com","DAYKEEPER_API_KEY":"<from credentials.json>","DAYKEEPER_MCP_ENABLE_PLANNING":"true","DAYKEEPER_MCP_ENABLE_MUTATIONS":"true","DAYKEEPER_MCP_ENABLE_INBOX_TOOLS":"true","DAYKEEPER_MCP_ENABLE_ACTIVATION_TOOLS":"true","DAYKEEPER_MCP_ENABLE_OPERATOR_TOOLS":"true"}}}}
```

## Backend usage

Run the management SDK on a trusted server. It has no default production API URL. The hosted API origin is https://api.mydaykeeper.com; the customer gateway is https://gateway.mydaykeeper.com.

```ts
import { DaykeeperClient } from "@skyporch/daykeeper";

const daykeeper = new DaykeeperClient({
  baseUrl: process.env.DAYKEEPER_API_URL!,
  apiKey: process.env.DAYKEEPER_API_KEY!,
});

const session = await daykeeper.customerSessions.create(tenantId, {
  purpose: "customer",
  subject: userId,
});

const conversations = await daykeeper.operatorConversations.list(tenantId);
const thread = await daykeeper.operatorConversations.messages(conversationId);
await daykeeper.operatorConversations.reply(conversationId, { body: draft });
```

The customer session token is short-lived and belongs to one end user. Never put a management credential in a browser or mobile client.

## Limits

- The Free plan includes one API inbox per workspace.
- The machine credential lasts seven days and rotates through the CLI.
- Keep the credential server-side, out of browsers, mobile bundles, source control, command arguments, and logs.
- Website and email inboxes still need the human console at https://app.mydaykeeper.com.
- Paid plans and overage budgets require a verified human owner. Autonomous paid signup is not certified.

## Hand the workspace to a person

```bash
npx @skyporch/daykeeper-cli claim --email you@company.com
```

Run this after init, from the same machine. It issues an owner invitation for that address and prints a link once. Send the link to that person; they sign in at https://app.mydaykeeper.com and own the workspace. The agent keeps its credential. Rerunning returns the pending claim without a link; `--reissue` revokes it and issues a new one, and `claim status` lists claims.

## Links

Canonical site: https://www.mydaykeeper.com
Agent onboarding: https://www.mydaykeeper.com/ai-onboarding
Developer interfaces: https://www.mydaykeeper.com/developers
Pricing: https://www.mydaykeeper.com/pricing
Human browser signup and sign-in: https://app.mydaykeeper.com
Independent agent signup: one-command CLI enrollment against https://api.mydaykeeper.com, with no human sign-in.

## Current access status

- Account creation: independent-agent Free onboarding is available through the CLI for the API inbox happy path. Human signup and sign-in happen in the console at https://app.mydaykeeper.com. Signup, provisioning, and traffic activation are separate steps.
- CLI: published on npm as @skyporch/daykeeper-cli.
- TypeScript and Node.js SDK: published on npm as @skyporch/daykeeper.
- React Native SDK: published on npm as @skyporch/daykeeper-react-native.
- Web SDK: published on npm as @skyporch/daykeeper-web.
- MCP: published on npm as @skyporch/daykeeper-mcp; local stdio server, not a hosted MCP endpoint.
- For the current version of any package, run `npm view <package> version`.
- iOS, Android, and Cordova SDKs: release candidates; no public registry release is promised yet.
- Flow definitions: management only; publishing a flow does not mean it executes against conversations.

## Published packages

- CLI: https://github.com/SkyPorch/daykeeper-cli
  Run: npx @skyporch/daykeeper-cli init
- TypeScript and Node.js: https://github.com/SkyPorch/daykeeper-node
  Install: npm install @skyporch/daykeeper
- React Native: https://github.com/SkyPorch/daykeeper-react-native
  Install: npm install @skyporch/daykeeper-react-native
- Web: https://github.com/SkyPorch/daykeeper-web
  Install: npm install @skyporch/daykeeper-web
- MCP: https://github.com/SkyPorch/daykeeper-mcp
  Install: npm install @skyporch/daykeeper-mcp

## Agent operating contract

1. Independent agent signup is available for the Free API inbox path; human sign-in is not a prerequisite. Run the CLI, keep the machine-owner signing key secure, and let the command store the credential. Paid plans and overage budgets require a verified human owner; autonomous paid signup is not certified.
2. Use a tenant-bound, revocable credential with the smallest required scopes.
3. Discover server capabilities before attempting a feature.
4. Plan first and apply separately with the exact plan version and a durable idempotency key.
5. Inspect long-running operations instead of guessing completion.
6. Treat a timeout or canceled write as an unknown outcome; reconcile before retrying.
7. Keep management credentials out of browsers, mobile bundles, source control, command arguments, and logs.
8. DNS, identity-provider, app-store, and other external-authority changes may require a human or external administrator. An API inbox needs none of them.

## Safety and commercial rules

- API and agent access are not enterprise-only add-ons.
- Daykeeper does not plan to charge per API credential, MCP connection, software-agent identity, or human seat.
- Overage is off by default and requires a verified human workspace owner plus a hard monthly budget.
- Existing history remains readable at a usage limit; accepted messages must not silently disappear.
- Monthly USD prices: Free $0, Pro $19.99, Scale $99.99 per workspace. Human Pro checkout and billing-portal return have been verified; autonomous paid signup is not certified. Inspect the workspace's current entitlement and usage limits rather than inferring them from SDK availability.

## Source and security

- Publisher: https://github.com/SkyPorch
- Report package vulnerabilities using the SECURITY.md instructions in the relevant public repository.
- Do not infer availability from a source branch, pull request, preview, or unreleased package version.