Pricing

Pricing will be finalized after discovery.

KORE1st pricing is not published yet. The right plan should be discussed after understanding your modules, companies, users, 5GB included storage, extra storage, own cloud, custom domain, own database, email sending setup, support, and onboarding requirements.

No public rates yet

Custom subscription scope.

A public pricing table can be added later when packages are decided. Until then, KORE1st can be positioned as a subscription-based business platform with 5GB default upload storage and plan discussion after demo.

Storage can be increased with additional charges, or the customer can request approved own cloud storage configuration.
Source code is not included in subscription pricing. Clients receive platform access and approved configuration options, not repository or deployment ownership.

Discussion factors

What affects subscription scope.

Modules required

CRM, inventory, HRMS, approvals, reports, notifications, templates, and other modules can affect subscription scope.

Company count

One subscription can manage multiple companies, and the required company structure should be reviewed during discovery.

Users and roles

User count, role complexity, permission needs, and approval responsibilities can change onboarding scope.

Custom domain

Domain/subdomain mapping requires DNS, SSL, verification, and activation effort.

Own database

Customer-owned database options require hosting, backup, security, connection, and responsibility planning.

Own email sending setup

Customer SMTP setup can require provider verification, DNS records, testing, and deliverability checks.

Storage requirement

5GB file upload storage is included by default. Extra storage can be increased with additional charges based on business requirements.

Own cloud storage

Customer-managed cloud storage setup can be discussed for Amazon S3, Azure Blob, DigitalOcean Spaces, Wasabi, Cloudflare R2, MinIO, or S3-compatible providers.

Media annotation

Image and video annotation requirements can affect module scope, storage usage, review workflows, and implementation planning.