devoffus turns Mike into Courier, with a migration warning attached

This fork is becoming a separately branded, hosted product rather than a lightly modified copy of Mike.

brandinginfrastructure

devoffus has renamed Mike to Courier across the product, from its interface and documentation to deployment settings and storage. There is no new legal-AI capability here, but it is a meaningful operational move: Courier is being presented as its own service.

The follow-up matters more than the new name. Existing Mike operators who adopt the rebrand must rotate the encryption setup used for stored connection credentials and move their cloud storage to the renamed bucket. Without that migration work, previously stored credentials can no longer be read and uploaded material may be left behind.

The fork also corrected links that had briefly pointed users to an unrelated freight company.

So what Worth a look for legal-tech teams considering a white-label deployment, especially if they need to preserve existing customer data during a rebrand.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from devoffus/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
f2106a15 chore: rebrand Mike to Courier Courier 2026-07-27 ↗ GitHub
6c63d352 docs: align courier.com references with app.courier.com + add Mike upgrade guide devoffus 2026-07-27 ↗ GitHub
commit body
The Mike->Courier rebrand left a few courier.com references pointing at an
unrelated freight company's registered domain. Realign them to
app.courier.com (the actual deployment, matching frontend metadataBase):

- README.md (banner image + website bullet)
- frontend/src/app/signup/page.tsx (terms + privacy links)
- frontend/src/app/support/page.tsx (URL placeholder)
- frontend/src/app/components/site-logo.tsx (production landing href)

Also adds an 'Upgrading from pre-rebrand Mike deploys' section to README
that documents the two operational breaking changes introduced by the
rebrand so existing operators know what to do at deploy time:

- Encryption salt rotation (user_api_keys + user_mcp_connectors rows
  encrypted with the old mike-*-v1 salts are unreadable across the
  courier-*-v1 salt flip; provides a SQL wipe path and a one-off
  re-encryption script path).
- R2 bucket rename (the default R2_BUCKET_NAME flipped from mike to
  courier; provides aws s3 sync + rollback commands).

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-982.md from inside the repo you want the changes in.

⬇ Download capture-thread-982.md