Changelog

What shipped. Weekly.

Strkr ships weekly, sometimes daily. This is the running public log. No marketing fluff, no post-dated announcements, no 'coming soon' entries. If it's here, it's deployed.

Start free trial See pricing
How to read this

Honest facts, dated, in the voice we write pull requests in.

Every entry below ships to production. Dev deploys that haven't promoted don't make the log. We treat the changelog as a signal of pace to anyone evaluating the platform: existing customers, prospects running a bake-off, journalists tracking the space. Keep it bookmarked.

Entries are terse by design. If a line here matters to your workflow and you want more context, hit the articles section for the deep dive or contact support and we'll walk through it.

Recent

The last six weeks.

SEO infrastructure and content push

  • SEMrush site audit integration complete. Full automated crawl and findings routed into the content ops queue.
  • Published 140 new /answers pages across the sales strategy, CRM migration, and demand generation clusters.
  • Structured data markup cleanup across the marketing site killed 7,000 schema errors. Rich results eligibility restored on every published page.
  • llms-full.txt generated and served from the marketing site root for AI retrieval agents.

Marketing site on prod stack

  • Marketing site migrated to the production CloudFront distribution. strkr.io now serves from the same edge as the app.
  • OLG Phase 2 shipped roughly 60 net-new landing pages for roles, features, and competitor comparisons.
  • Dev-stack teardown parked for a controlled cutover: 20 ghost URNs flagged for the next infrastructure pass.

Salesforce migration path

  • Salesforce classic Connected App integration shipped. OAuth round-trip against production Salesforce orgs working end to end.
  • Preview sessions for data migration: inspect a Salesforce org's objects, field mappings, and record volumes before writing anything.
  • Commit sessions pull the data in via the standard Strkr API, same consent and audit controls as any native write.

F19 flows audit pass

  • Eighteen P2 fixes across the flow builder, flow runtime, and flow debugger.
  • Three DRY refactors lifted repeated patterns out of trigger handlers and action handlers.
  • Closed all 68 remaining findings from the F16 audit. Flows surface is at zero known-defect for the first time since the module landed.

Per-workspace subdomains

  • Production subdomain routing live. Every new workspace gets a {slug}.strkr.io origin at sign-up.
  • Prod-tier feature-flagged for a controlled rollout. Existing workspaces opt in from Admin.
  • Dev stack stays on a single origin to keep local workflows fast. Prod picker hops from app.strkr.io to the workspace origin on login.

Public status page

  • status-prod.strkr.io and status-dev.strkr.io live.
  • Six-component green/red health view: API, web app, auth, database, messaging, and background workers.
  • Incident posts and historical uptime rendered from the same source the on-call rotation reads.
Earlier

September and the launch of Messaging.

Strkr Messaging billing locked

  • Full markup table on SMS and MMS usage locked for the September launch.
  • Dunning flow wired: failed messaging invoices pause the messaging module without touching the base subscription.
  • Carrier fee passthrough reconciled against monthly invoices. No hidden surcharges, no retroactive catch-ups.

Strkr Messaging module

  • SMS and MMS module live for every tenant that opts in. Pricing is $29 per month base, 2 cents per SMS segment, 5 cents per MMS.
  • Consent gates every send-path. 409 CONSENT_DENIED surfaces to the composing user with the reason inline, no retries.
  • Auto-STOP keyword handling, quiet-hours enforcement in the contact's timezone, carrier segment counting at compose time.
  • Public API endpoint at POST /v1/messaging/send covers the same consent and metering pipeline as the in-app composer.
What we log and what we don't

The editorial line behind every entry.

Every entry on this page meets three bars. One: it shipped to production, verified in a prod smoke test, not a dev deploy and not a feature flag that still gates the thing from most tenants. Two: a customer could reasonably care, which rules out internal refactors, test-coverage bumps, and dependency upgrades. Three: it's described in the voice we write pull requests in. No campaign copy, no superlatives, no 'exciting new'.

What we don't log: security patches that would hand attackers a map of what to try, pricing experiments on the marketing site, internal tooling improvements that don't affect the product, and any work in progress on a branch. If an entry would mislead a reader about the state of the platform, we don't ship the entry.

Entries can be edited post-publish for clarity or to add context. Factual corrections are called out inline rather than silently swapped. If a feature we announced here was later rolled back, that rollback gets its own dated entry.

Follow along

How to track the log without checking back here.

Try the platform

The log reads better from inside the product.

Start a 14-day trial See pricing

Starter is $29 per seat per month, Pro is $59, Scale is $119. Every tier includes the full API surface, custom objects, field-level permissions, and the modules on this changelog.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing