How many custom objects can I create on Strkr?
Strkr supports hundreds of custom objects per tenant on every paid tier with no additional seat lines or tier upgrades required. The custom object surface includes real schemas (field types, required fields, default values, validation rules), relationships to other objects (lookup, master-detail, many-to-many), permissions per object, custom views, and reporting. The pattern suits teams modeling complex business shapes (multi-sided marketplaces, specialized verticals, complex product catalogs) without hitting the custom object count limit that legacy CRMs enforce.
What are the API rate limits on Strkr?
Strkr publishes API rate limits per tier on the developer docs with specific numbers for requests per minute and requests per day. The limits are set generously relative to typical integration patterns, so most teams do not hit the limit under normal operations. The admin console shows current usage against the limit so throttling is predictable rather than surprising. Enterprise tier has higher published rates for high-volume integration scenarios. The rate limits are not negotiable at purchase but the published numbers suit the vast majority of use cases.
Are webhooks available on every paid tier?
Yes. Strkr webhooks are available on every paid tier with configurable event filters (which records, which actions, which conditions), delivery retry on failure, signature verification for security, and payload customization. The webhook admin console shows delivery logs with payload, response status, and retry history for debugging. Failed webhooks can replay to the endpoint with the original payload. The webhook surface is first-class, not an Enterprise-tier upgrade gate as it often is on legacy CRMs.
How does Flow handle external API integration?
Strkr Flow includes an HTTP action node with typed request (method, URL, headers, body, auth), typed response (status, headers, body with JSON parsing), OAuth handling, retry policy with configurable backoff, and error branching. External integrations (enrichment APIs, custom services, legacy systems) build inside Flow without a secondary automation tool. The HTTP action handles REST APIs, authenticated endpoints, and most common integration patterns. Teams typically consolidate a prior third-party automation tool into Strkr Flow for CRM-adjacent automations.
What is the authorization model on Strkr?
Strkr uses claims-based authorization with row-level security on every table. Claims express as predicates that evaluate against user attributes (role, team, territory, department), record attributes (owner, stage, status, custom fields), and context (time, region, source). Business rules like "the AE can read deals in their territory but only edit deals they own" express as claim predicates in the admin console. The model is substantially more expressive than role-only authorization and handles real-world business rules without workarounds. Permissions evaluate at query time, so changing a claim affects data access immediately.
How deep is the Strkr audit log?
Strkr audit logs capture every write with field-level before and after values, actor (user, API token, Flow definition), timestamp with millisecond precision, source (user action, Flow execution, API call, integration), and context (session, IP, user agent). The audit log is queryable through the admin console with filters by actor, time range, action type, object type, and record. The audit log exposes via REST API for integration with GRC platforms, SIEM tools, and custom compliance workflows. The pattern satisfies HIPAA audit review requirements and other regulated-industry compliance scopes. Strkr is HIPAA compliant with Business Associate Agreement available on request, SOC 2 Type II in progress through 2026-Q4, GDPR and CCPA compliant.
