Plan for the unified profiles you manage and the data operations you run. Choose the deployment, engineering support and implementation help your team needs.
Allowances are proposed totals across the included workspaces. Unified profiles include identified and anonymous profiles. Production and test count as separate workspaces. Every plan includes deterministic, configurable and reversible identity resolution. Its usage counts toward Data operations only on Krenalis-managed databases, per source identity included in each run.
Usage / Proposed capacity packs
Two clear measures of usage.
Unified profiles measure how many profiles you manage. Data operations count event and record ingestion, plus identity resolution on Krenalis-managed databases.
Unified profiles
Count all unified profiles currently managed, including identified and anonymous profiles, whether active or inactive. Historical profile versions are not added together. This profile allowance applies with a Krenalis-managed database or your own warehouse.
Proposed capacity pack
+100,000 unified profiles $50 / month
Data operations
Each ingested event or record counts as one operation. With a Krenalis-managed database, also count one operation for each source identity included in each identity resolution run, including reruns. With your own warehouse, identity resolution does not consume Data operations.
Proposed capacity pack
+1 million monthly data operations $50 / month
Capacity packs are proposed additions for paid plans, not automatic overage charges. Agree any extra capacity or plan change with us in advance. Free has no automatic paid usage.
Are identified and anonymous profiles counted separately?
No. Both share the Unified profiles allowance, with no separate anonymous activity window. Count the current unified profiles, including inactive ones. Historical profile versions are not added together. This allowance applies with either database choice.
How is identity resolution usage counted?
Only with a Krenalis-managed database: count one Data operation for each source identity from the configured data sources included in the run. A run using 10,000 identities counts as 10,000 operations, even if it produces 1,000 unified profiles. Rerunning on those identities adds another 10,000 operations. With your own warehouse, identity resolution does not consume the allowance.
What capacity is separate from these allowances?
Confirm database storage, retention, backup scope, payload sizes and destination delivery capacity for your setup. Event and record ingestion, including repeat imports, use Data operations in both setups. Identity resolution adds usage only on Krenalis-managed databases. With your own warehouse, your provider bills its storage and compute separately.
Get technical help from the Krenalis engineering team. Discuss the onboarding and implementation work needed to take your use case into production.
Commercial product support
Keep Krenalis working.
Get help with product issues, official warehouse connectors, APIs and security configuration. Managed Cloud maintenance and patches are covered by the current support policy.
Discuss help with source and destination setup, event mappings and identity rules. Custom integrations, data modeling and project delivery need a separately agreed scope.
Agree the initial setup, validation and operational handover for your deployment. Define deliverables, responsibilities and any services fee before the engagement starts.
Starter proposes standard commercial support and Growth proposes priority support. Coverage follows the applicable agreement and Support Policy. Guided onboarding, solution engineering and implementation work are scoped separately.
Know how to reach us.
Customers with an active commercial support agreement have private technical support from the core engineering team. Open tickets through support@krenalis.com. Enterprise tiers also have a dedicated Slack channel.
Standard support hours are Monday–Friday, 09:00–18:00 CET/CEST, excluding official public holidays. Enterprise P1 coverage extends to 24/7/365.
Community support uses public GitHub Issues and Discussions on a best-effort basis, with no guaranteed response times. Commercial support packages for self-hosted deployments can be discussed separately.
Critical block with no workaround: response target within 4 business hours. Enterprise P1 coverage extends to 24/7.
P2 / High
A major feature or connector is impaired, with a workaround available: response target within 24 business hours.
P3 / Normal
General assistance, minor issues and configuration questions: response target within 48 business hours.
These response targets summarize the current Support Policy. Response time and resolution time are different; the policy and your applicable agreement define coverage and commitments.
Two separate decisions
Choose where data lives. Choose who operates Krenalis.
A managed Krenalis service and a managed customer database describe different parts of the setup.
Krenalis-managed database
Start Free or Starter with Krenalis-managed PostgreSQL. No existing warehouse is needed. Confirm database capacity, retention, hosting and data processing terms with us.
Connect your PostgreSQL or Snowflake warehouse with Starter or Growth. Krenalis remains managed in our cloud. Identity resolution does not consume Data operations on your own warehouse; event and record ingestion still counts. Your provider bills warehouse compute and storage separately. Discuss managed alternatives for Growth with us.
Enterprise deployment options. Krenalis Cloud is hosted and managed by us. You can also discuss Bring Your Own Cloud (BYOC), managed by Krenalis in your cloud account, or self-hosted, operated by your team. Availability, deployment scope, operational responsibilities and support are agreed for your project.
Free Cloud is the proposed managed service with quotas. Community is software you install and operate under its licence; you provide and manage the infrastructure.
Cloud plan allowances are separate from the Community licence. Review the licence terms for your intended use, especially when delivering services to third parties.
Community / self-hosted
Run it in your environment.
Set up Krenalis and the workspace database yourself. Commercial support and service requirements can be discussed separately.