Custom services

When the product is not enough: integrations, development and support

The Kamzan ecosystem covers most cases. For the rest, there is us: we connect Kamzan to the systems you already use, build what is missing and support your team from day one.

Tell us about your case Projects delivered

How we work before a quote: the consulting path

Features born from a request

Many of today’s standard features started as a dedicated development for one customer. Then we made them available to everyone: that is how the product grows.

  • Auditor role Requested by a bank
  • File expiry dates Requested by an insurance broker
  • Print, download and screenshot block Requested by a multinational
  • Watermark on PDFs Requested by a data room customer

Integrations with the systems you already use

Management systems, signature providers, compliant archiving, SMS delivery, third-party apps: Kamzan exposes APIs and webhooks that over the years we have used to connect very different systems. Every integration is designed with the same care for data handling as the product.

  • Healthcare system → reports to the patient

    A clinic’s management system deposits reports in Kamzan; the patient receives the link and a password by SMS to download them securely, without signing up.

  • Management system → contract signing flow

    A management system generates the contract and drives the whole signing round inside Kamzan, from sending to archiving the signed document.

  • Compliant archiving and signature providers

    Sending any file on the platform to compliant long-term archiving, and signing flows with the provider chosen by the customer, without changing how users work.

  • External apps reading documents

    A partner’s Android app accesses a specific part of the Kamzan archive: people in the field see only the documents they need, with the platform’s permissions.

Dedicated development

When the right app does not exist we build it: inside Files as a dedicated feature, or as a standalone application that joins the ecosystem with the same login, the same European servers and the same privacy rules.

  1. Free analysis

    A call to understand the process, who uses it and what needs to change. The outcome is a clear scope and a quote.

  2. Privacy-by-design planning

    Minimal data, explicit permissions, activity logs: the product’s rules apply to custom work too.

  3. Short release cycles

    Intermediate versions to try on real data, so corrections come before delivery rather than after.

  4. Maintenance and evolution

    What we build stays up to date with the platform. If it serves several customers, it becomes a standard feature.

Projects delivered

Onboarding and training

Software works when people use it. That is why going live is not an activation link: we configure together, migrate the data and train the people who will work on the platform every day.

  • Initial setup and migration

    Folder structure, profiles and groups, brand, domain. We bring the existing archive over from servers, NAS or other clouds with the migration tool.

    Desktop, sync and migration

  • Team training

    Video-call sessions for administrators and users, on your real cases: who shares what, with whom, with which permissions.

    Permissions, profiles and groups

  • Ongoing support

    Support from the people who build the platform, step-by-step online guides and a point of contact for custom projects.

    The help centre

Frequently asked questions

How much does an integration or a dedicated development cost?

It is quoted after a free analysis of the case. The quote states scope, timing and a fixed price; later evolutions are quoted separately.

How long does it take?

A typical integration with a management system takes a few weeks; a dedicated application from one to a few months, with intermediate releases to try. Timing is in the quote.

Does Kamzan have APIs?

Yes: the platform exposes APIs and webhooks to exchange files, metadata and events with external systems. During the analysis we work out together which ones fit your case.

Who maintains what gets built?

We do: developments stay aligned with platform updates and are covered by support. If a feature is useful to other customers it can join the standard product, at no extra cost for whoever requested it.