What's NewCopy Anchor Link

v1.0 — HotCRM, the CRM that rewrites itselfCopy Anchor Link

The first launch. HotCRM v1 is for teams who are sick of waiting on their CRM vendor to add the field they need next quarter. You add the field; the AI uses it the next time you ask. Three things in this release make it different from every CRM you've used before.

✨ Wow #1 — Live schema, live AICopy Anchor Link

Add a field in the admin console. Ten seconds later, ask the AI assistant a question about it. It already knows. No retraining, no restart, no redeploy — the platform re-reads metadata on every agent turn and the Copilot's describe_object tool returns your new field as soon as it's saved.

Try it in 30 seconds with the script we ship:

HOTCRM_TOKEN=... ./scripts/wow1-live-schema.sh

💬 Wow #2 — Chat-first record pagesCopy Anchor Link

Open any account, opportunity, case, or contract. The Copilot is always one click away in the floating chat bubble — and it already has the live schema and this record in scope. Ask:

• "Give me the full picture of this account."
• "Draft a follow-up email to the primary contact."
• "What are the next 3 actions I should take?"

The discussion feed at the bottom of every record page captures the back-and-forth so it stays as institutional memory, not a Slack thread that nobody can find next quarter.

🛠️ Wow #3 — Honest about what's in the boxCopy Anchor Link

We don't pretend the platform does things it doesn't. The natural- language flow builder is a platform capability we've designed (ADR-0010) and is on the roadmap, but doesn't ship in v1. What does ship: every business object, view, page, dashboard, role, and seed record is a plain TypeScript file you can edit, diff, and commit — and the AI sees those edits the moment you save.

What's in v1.0Copy Anchor Link

• 15 business objects across Sales / Service / Marketing / Revenue.
• Sales Copilot with 5 skills: live data, lead qualification, email drafting, revenue forecasting, customer 360°.
• Executive Dashboard + 9 pre-built reports.
• Slimmed nav — 5 core surfaces (Sales, Service, Insights, Approvals) so a new user can find their way around in 30 seconds.
• Demo seed — Acme Corporation is a fully-formed customer (3 opps, 2 cases, 1 contract, 3 narrative tasks, a 1KB strategic brief) so the Copilot has real material to summarize the moment you log in.

Ready to try? pnpm install && pnpm demo:reset && pnpm dev, then open http://localhost:4001 and create the first admin account.

v4.0.1 — Latest releaseCopy Anchor Link

HotCRM 4.0.1, running on ObjectStack 17.7.0 across every @objectstack/* package. The app manifest declares the matching ^17.7.0 protocol range, so a runtime on a different protocol major refuses the load up front with a structured diagnostic instead of failing deep in a schema parse.

This page does not keep a second release table. The release-by-release history is CHANGELOG.md in the repository, compiled from the .changeset/ entry every pull request adds. The versions between v1.0 and 4.0.1 are recorded there and are deliberately not re-listed here — a hand-maintained copy of that history is exactly how this section came to advertise a "v5.0" that was never an app version, on a platform major that never shipped it.

4.0.1 is the first 4.x release that installs from the marketplace. 4.0.0's marketplace publish carried an empty app and was withdrawn, so a deployment on 3.x upgrades straight to 4.0.1, and everything under "What 4.0.0 adds" below, the checks before upgrading included, applies to it. 4.0.1 also makes the sidebar logo and favicon show on hosted installs.

What 4.0.0 addsCopy Anchor Link

4.0.0 is a major because a contact's mailing address becomes one field. The five separate address fields are removed, and an existing deployment converts its contacts' addresses once (see the checks below). The release also records more of each sale.

• The sales records carry more of the deal. An account records who it is on paper, what it spends, what it may be sold and whether it has been signed off. A contact records the buying centre: their role in the purchase decision, where they stand on you, and how well you know them. A lead records what the prospect needs and roughly what it is worth. An opportunity records whether it is worth pursuing, the customer's own procurement calendar and the story behind the deal.
• Sign-offs where the company commits. Qualification approval (立项) before a deal's stage can move, and sign-offs on an account's registration, a lead's conversion and a deal's won/lost call. The lead, qualification and won/lost gates ship switched off; an administrator turns each one on.
• Every notification arrives in the recipient's own language. One alert addressed to a Chinese-speaking rep and a Japanese-speaking manager reaches each of them in their own language.
• Quotes and contracts follow the account. A rep now reads the quotes and contracts of every account they can see, renewals included.
• A contact's mailing address is one field, shown and edited as one unit, the same shape as an account's billing address. The contact import template keeps its five address columns.
• HotCRM installs as one app carrying two packages: the HotCRM app and its Service module, which holds cases and knowledge.
• The platform line moved from 17.4.0 to 17.7.0, in three steps, every @objectstack/* package together with the protocol range the manifest declares.

Plus a long tail of fixes, each with its own entry in CHANGELOG.md.

Check these before upgrading:

• Convert the contact addresses once, before os migrate apply --allow-destructive. Upgrading does not move a contact's old address fields, and that command deletes them. The mailing-address entry of CHANGELOG.md gives the two commands.
• An integration that reads or writes mailing_street … mailing_country on a contact must use mailing_address and its parts instead.
• My Cases is now the last item of My Work. Every other menu entry is where it was.
• A write to a record the caller cannot see now answers 404, where it answered 403 before.
• Imports read dates strictly. A month-first cell such as 07/15/2026 now fails its row instead of importing as a different date.

What 3.1.0 addsCopy Anchor Link

A minor release: nothing is renamed, no stored record is rewritten, and an upgrade from 3.0.0 needs no migration step.

• A Claim Case button. Taking an unowned case out of Unassigned — triage already worked — an agent moves it to a working status and the claim seam stamps them as the owner — and nothing on screen said so. The gesture now has an action on the case record header and in the triage row menu: it asks which working status you are claiming into, defaulted to In Progress, and moves the case there. It deliberately does not write ownership; the claim seam remains the only writer of that column.
• The platform line moved from 17.1.0 to 17.4.0, in three steps, every @objectstack/* package together with the protocol range the manifest declares. Nothing an author writes in src/ changes shape.
• A SaaS / multi-organization composition, for an operator running one HotCRM deployment on behalf of several organizations.
• The knowledge base's Review Queue tab is gone. It returned every published article sorted least-recently-reviewed first, which degrades into "all articles, different sort" as a knowledge base grows. last_reviewed_at is untouched — only the tab that ranked by it is removed.
• The product catalog's Default Tax Rate % is gone. crm_product.tax_rate could be set only through the REST API and no total anywhere read it. Tax is unchanged where it is actually computed: the quote line item's own rate, and the Tax amount on the quote.

Plus a long tail of fixes, each with its own entry in CHANGELOG.md.

The one thing to check before upgrading: an integration that writes crm_product.tax_rate over the REST API. That field no longer exists, so the write is refused rather than ignored. Nothing else in this release removes or renames anything a client can address.

Upgrading from 2.x — Owner is now one fieldCopy Anchor Link

3.0.0 is a major because reassigning Owner now moves access. Before it, every business object carried two owners: the Owner on forms, views and reports, and a separate hidden column the platform used for every access decision. Nothing kept them in step — changing Owner moved the record in every list and report and moved no access at all. The previous owner kept it; the new owner never got it.

HotCRM now has exactly one Owner: the platform's ownership column.

What this means for an existing deployment:

• Reassignment is gated separately from edit rights. Because it really does transfer access, changing Owner is its own permission rather than a side effect of being able to edit the record.
• Run the backfill once. Deployments where somebody reassigned an Owner under 2.x have the two columns out of step; pnpm backfill:owner reconciles them. It never blanks an existing owner and is safe to re-run — and it needs an administrator account, because a bulk transfer is what it performs. If nobody ever reassigned an Owner, the columns already agree and the backfill reports zero divergences.

The full entry — including the per-persona reassignment table — is the Major Changes section of CHANGELOG.md.

Where the current shape of the product is written downCopy Anchor Link

Rather than restate the inventory here — where nothing would check it — each area is described on the page that owns it, and those pages are held to the registered metadata by the repository's docs-drift guard:

• What ships in the box — Introduction.
• Dashboards, reports, and the datasets underneath them — Analytics.
• Profiles, positions, and sharing — Sharing & security.
• The AI surface — AI assistant. HotCRM ships skills only; they attach to the platform assistant, and the app defines no agent of its own.

RoadmapCopy Anchor Link

What we're working on next:

• Forecasting AI improvements — better confidence intervals, what-if scenarios.
• Service workforce management — agent scheduling and capacity planning.
• Marketing journey designer — multi-step nurture campaigns.
• Mobile app — native iOS and Android for field reps.
• More connectors — Slack, Microsoft Teams, Google Workspace, HubSpot import.

Suggestions? File an issue on GitHub.