Annual licence
Proposed licence for an agreed isolated instance.
Pricing
Pricing that follows brands and markets.
Supakraft is proposed as an isolated instance with a guided setup. The scope and operating terms are agreed for each deployment. Pricing follows brands, markets and usage rather than primarily user count.
Setup
One-off. Establish brand truth, configure scope and control, accompany the first governed runs.
Operation
Proposed monthly operation and monitoring of the agreed instance.
The concrete price depends on brands, markets and usage volume. After a short audit you receive a proposal.
Frequent questions
- Why not per user?
- A control layer that applies only to paid seats leaves part of the work ungoverned. The pricing logic therefore follows brands, markets and usage.
- How does the introduction work?
- Guided, in four steps: establish brand truth, configure scope and control, first governed run, first human approval. The larger part of the work sits before the first login.
- How is supakraft operated?
- The target model is a separately operated instance per client. The concrete isolation and access arrangements are agreed and verified before productive processing.
- Where is my data processed?
- Data regions and subprocessors are confirmed in writing per instance before productive processing. The security review contains the current processing chain.
- What happens if we stop?
- Brand Truth sits in the Brand Definition, a documented, machine-readable format. Export, retention and deletion are defined in the client contract and the respective deployment.
- Is there a pilot?
- A bounded pilot can be scoped on a dedicated instance. Its content, readiness and operation are agreed in the proposal.