On-premise deployment
This is not a product you can buy today. On-premise deployment is a Wave 3 Enterprise conversation, not a shipping option, and there is no committed date.
In short
On-premise deployment of KanchanFlow is not generally available. Our standard deployment is our USA data centres on AWS US-East and US-West. On-premise or customer-cloud deployment is a Wave 3 Enterprise conversation with no committed date and no published price, and it is listed as Contact Sales in our feature matrix for that reason.
Where this actually stands
Some manufacturers cannot put customer data in a vendor's cloud — an ITAR obligation, a defence customer's requirement, or an internal policy that predates the argument. We would rather have that conversation honestly than pretend a self-hosted build exists. Most requirements described as on-premise turn out to be data residency or audit requirements, and those have a different and much shorter answer.
It does not. Today the product runs in our USA data centres, on AWS US-East and US-West, with no offshore replication. Enterprise customers with a genuine on-premise requirement should talk to us about what is possible and on what timescale, and the answer may be that we are not the right fit yet.
Capabilities
What this would cover if we build it
What exists today
USA data centres on AWS US-East and US-West, with no offshore replication, plus custom data residency as an Enterprise capability. That is the current answer to a data location requirement.
What Contact Sales means
A scoping conversation, not an order form. There is no published price, no packaged installer and no standard support model for an on-premise deployment.
Why it is hard
The AI agents, the WhatsApp Business API connection and the e-invoicing integrations all reach external services. An on-premise deployment has to answer what happens to each of those.
Enterprise only
If it becomes real, it is an Enterprise capability. Our feature matrix lists on-premise as Contact Sales under Enterprise and blank on the other tiers.
What we would ask you first
Which requirement is actually binding — where data is stored, who can audit it, or whether any external call is permitted at all. The three have very different answers, and only the third genuinely needs an on-premise build.
Step by step
Where the work stands
There is no workflow to walk through yet. This is what the current position actually is.
- 1
There is no installer
There is no packaged on-premise build. Anyone telling you a date for one at this stage would be guessing.
- 2
Start with the actual requirement
Most on-premise requirements are really data residency, data sovereignty or an audit requirement, and Enterprise custom data residency may already answer them.
- 3
Scope the external dependencies
AI agents, WhatsApp and e-invoicing all call out. Any deployment discussion has to establish which of those you can and cannot allow.
- 4
We may say no
If your requirement is a fully air-gapped install, we are not the right vendor today, and we will tell you that in the first call rather than the third.
What this is not
This is not a shipping deployment option — there is no on-premise build available today, at any price, on any tier.
This is not an ERP, MRP, CAD, BOM, or advanced CPQ system — it manages customer RFQs, quotes, follow-ups, and order handoff.
Tier availability
What you get on each plan
These rows come from the same feature matrix the pricing page publishes. If the two ever disagree, the matrix is wrong and we fix it.
| Plan | Availability |
|---|---|
| Starter | Not available. |
| Professional | Not available. |
| Enterprise | Contact Sales. Not a shipping option — a scoping conversation with no committed date. |
Starter is $39 per user per month, Professional $49, Enterprise $99 plus a $2,000 monthly platform fee. Annual billing is 17% lower. See the full matrix.
Interface
What it looks like
No screenshot. There is no on-premise build to capture.
We do not publish mockups of unbuilt capabilities as if they were interface captures.
No screenshot. See the Trust Center for our current USA data centre and residency position.
Placeholder retained so this page's structure matches every other feature page.
Screenshots are described rather than mocked up. Captures are taken from the build current at the date shown in the changelog, on a sample workspace.
Questions about on-premise deployment
No. There is no packaged on-premise build today. Our deployment is USA data centres on AWS US-East and US-West with no offshore replication.
Related features
SSO
SSO — SAML, Okta, Azure AD, Google Workspace
Read moreMulti-company and multi-plant
Multi-company and multi-plant
Read moreImmutable audit log
Immutable audit log for compliance-driven manufacturers
Read moreWhat's shipping today
All 47 features grouped by status on one page, with the newest releases alongside.
Read moreSee a live quote draft built from a real RFQ
Fourteen days, no credit card, sample data pre-loaded. If it does not fit your shop, we will tell you in the first call.
- Delaware LLC
- SOC 2 Type II
- USA Data Centers (AWS)