Strkr is marketing automation delivered as true multi-tenant SaaS. Seat-based pricing, published uptime targets, documented data egress, open REST API, signed webhooks, and a single audit log per tenant. The platform runs on standard cloud infrastructure with a clear security posture and a path out that is written on the contract rather than negotiated at renewal.
Marketing automation delivered as SaaS carries a set of expectations. The finance team wants the invoice to be predictable. The security team wants evidence of controls. The data team wants a leave-the-platform plan on day one. The nine properties below are what the three teams want in common when they review a marketing automation SaaS vendor, and the ones Strkr is designed to carry on the contract rather than negotiate at renewal.
Strkr runs as a single multi-tenant platform. Each workspace is isolated at the data layer and the audit layer. Shared infrastructure is where the efficiency comes from; tenant isolation is where the trust comes from.
Pricing is per user seat. The invoice does not reprice on marketable contact count, event volume, or send volume. Finance models the yearly cost with headcount growth, not database growth.
Strkr publishes an uptime target and runs a public status page at status.strkr.io. Incidents are posted during the event with timeline updates. The SLA is a document, not a conversation.
Contacts, journeys, events, campaigns, attribution rules, and the audit log all export in documented formats. The egress plan ships with the contract so legal does not negotiate from a cold start at renewal.
The REST API, the webhook subscriptions, the audit log API, and the warehouse sync are all included on every paid tier. The platform does not gate the data layer behind an enterprise upgrade.
SAML and OIDC login handlers plus SCIM provisioning ship on every workspace. The ops team manages access through the IdP it already runs.
Data is encrypted at rest with managed keys and in transit with TLS 1.2 or newer. The security review packet documents the posture and the backup plan.
Every write across marketing and sales lands in one audit log per tenant. SOC 2 Type II evidence collection, GDPR data requests, and internal investigations all read one log.
Strkr publishes a changelog and a near-term roadmap. The feature set the buyer sees in the demo is the one the operator gets at go-live, not a promised line item that lands next year.
Marketing automation SaaS pricing has consolidated around a handful of patterns that compound the renewal invoice without compounding the value. The seven patterns below are the ones Strkr intentionally does not use, and the reasons each one looks fair at purchase but hurts at year two.
Vendor meters marketable contacts and bumps the tier at 10K, 25K, 50K, 100K. Suppression lists do not reduce the count on most tiers. The year two invoice is 40 to 60 percent larger than year one on nothing but list growth.
Some vendors meter sends. The invoice goes up when the team runs a product launch. Finance cannot model the next quarter because the usage is correlated with success.
REST API, webhook subscriptions, and warehouse sync all require an enterprise upgrade. The data team gets throttled unless the invoice goes up. Strkr includes the API on every paid tier.
The AI chapter ships as a separate SKU with a per-prompt credit meter. The buyer who thought AI was included gets a surprise invoice line item. Strkr AI is native on every paid tier.
SSO is a security control, not a convenience. Vendors that gate SAML and SCIM behind the enterprise tier push security posture onto the invoice. Strkr includes SSO on every paid tier.
Uptime targets, status page URLs, and incident postmortems should be published, not negotiated case by case. Strkr publishes the posture.
Vendors that charge for data egress or require a services ticket to export the journey graph are keeping the renewal easy to win. Strkr ships the egress plan with the contract.
Running a multi-tenant marketing automation SaaS at mid-market scale requires that nine operational properties be on day-one defaults. The nine below are the ones Strkr carries at every workspace size, from the two-seat small business to the fifty-seat mid-market account.
New features ship continuously behind feature flags, rolled out per tenant with a backout plan. The customer base sees the changelog with the behavior, not a quarterly block of changes to absorb all at once.
Backups run on a documented schedule with retention and encryption. Point-in-time restore for data corruption is available on the enterprise tier. The RPO and RTO are published, not negotiated.
Every API call, every webhook delivery, every journey step is traced. When an incident happens, the engineering team debugs from logs and traces, not from customer tickets. The audit log carries the artifacts the ops team needs.
API rate limits, webhook retry policies, and bulk endpoint limits are documented. The data team does not learn the numbers by hitting a 429 at 03:00.
The public status page at status.strkr.io posts incidents during the event with timeline updates. Postmortems are published within five business days.
Every row carries a tenant id. Query middleware enforces the scope. The audit log records tenant-scoped reads and writes. Multi-tenancy is a correctness property, not an efficiency property.
Strkr is HIPAA compliant with a BAA available on request, GDPR and CCPA compliant, and SOC 2 Type II is in progress through the fourth quarter of 2026. The compliance packet is available to prospects under NDA.
API versions are explicit on the request. Breaking changes land on a new version with a documented sunset window and a migration guide. The data team does not get surprised.
Seat-based pricing by tier is published on the pricing page. The buyer models the budget without a scoping call. The procurement team runs a side-by-side quickly.
A SaaS vendor that prices on seats, publishes uptime, ships continuously, and documents egress produces a different renewal conversation than one that reprices on list growth and gates the API behind the next plan. The six outcomes below are what finance and procurement should see when year one closes and year two is up for signature.
The year two invoice tracks headcount growth and tier CPI, not database size. Finance plans the budget with real numbers.
The security review packet (encryption posture, backup posture, compliance evidence) is on file. Procurement moves to the commercial conversation faster.
The roadmap is published. Operators plan quarters with evidence of what is coming instead of a sales-only promise.
The data layer and the automation layer both export cleanly. Renewal leverage sits with the customer, not the vendor.
GDPR, SOC 2 Type II, and internal investigations all read the single tenant audit log. Response time collapses.
Draft copy, score with reasons, segment on intent, time sends to the recipient clock. The assistant lives on the record on every paid tier.
A SaaS posture is best read through the artifacts the platform actually hands the customer. The six artifacts below ship on every Strkr tenant and are the ones security, finance, and ops teams typically ask to see during a procurement cycle. Each one is observable in the admin surface rather than described in a sales deck.
The public status page at status.strkr.io carries the live status of every subsystem, recent incident history with postmortems, and the uptime trend over the last ninety days. Nothing is hidden behind a sales conversation.
The egress document lists every exportable record type, the format of the export, the API endpoint used to retrieve it, and the warehouse sync destinations supported. The document ships with the contract so legal does not negotiate at renewal.
The security review packet carries the encryption posture, the backup posture, the HIPAA BAA template, GDPR and CCPA posture, and the SOC 2 Type II in-progress evidence. The packet moves procurement from skepticism to review quickly.
The audit log API exposes the compliance record to automated tooling. The security team runs weekly queries for configured events, the GRC team pulls evidence for the SOC 2 audit, and the DPO retrieves records for data subject requests directly.
The API spec is public, versioned, and carries sunset windows on breaking changes. The data engineering team integrates against known numbers. No vendor-managed SDK sits in the critical path.
The pricing page carries the seat-based tiers, the features included at each tier, and the add-ons available. Procurement runs the side-by-side without a scoping call. The budget conversation starts with real numbers.
A 20-minute tour of the admin surface, the audit log, the egress plan, and the status page. The posture is on paper, not in a sales deck.
Every row in the data model carries a tenant id, query middleware enforces the scope, and the audit log records tenant-scoped activity. The platform runs on a single codebase with shared infrastructure and isolated data, which is the efficiency and trust posture SaaS buyers expect.
Strkr prices per user seat. The invoice does not reprice on marketable contact count, event volume, or send volume. Finance models the yearly cost with headcount growth rather than database growth, and procurement can run a side-by-side from the published price card.
Strkr publishes a public status page at status.strkr.io with incident updates during the event. Postmortems are published within five business days of resolution. The uptime target is published on the SLA, not negotiated case by case.
Contacts, journeys, campaign-member rows, attribution rules, attribution output, and the audit log all export in documented formats. The plan ships with the contract so the data team does not negotiate at renewal from a cold start.
Strkr is HIPAA compliant with a BAA available on request, GDPR and CCPA compliant, and SOC 2 Type II is in progress through the fourth quarter of 2026. The compliance evidence packet is available to prospects under NDA.
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.
