Control should survive a change of developer.

Keep control of the assets needed to run the system.

The agreed delivery places the source repository, infrastructure accounts, database, data, credentials, deployment and operating documentation under your company’s control.

The architecture uses mainstream technologies, documented dependencies and no mandatory Calibre runtime or compulsory Calibre subscription.

Those controls are paired with clear rights for each part of the application:

• Custom code: the agreement specifies the ownership or license rights your company receives.
• Reusable Calibre components: retained rights and your rights to use them are identified separately.
• Open-source components: applicable licenses are documented.
• Third-party software and services: licenses, fees and external dependencies remain visible.

Calibre may reuse generic components and know-how, but not your confidential data or proprietary business logic. Ownership, licensing and access rights are defined in the agreement before implementation.

Have someone outside the build team prove they can run it.

Before final acceptance, an engineer outside the build team must successfully:

• Deploy the application from the customer-controlled repository.
• Restore it using the documented backup procedure.
• Demonstrate that it can be operated without Calibre.

The test uses your infrastructure and documentation. If it does not pass, portability has not met acceptance.

This makes the freedom to choose another provider a delivery requirement with a practical test.

Choose your provider—and plan for the work that remains.

Owned software still needs monitoring, backups, updates, incident handling and someone responsible for its operation.

Calibre includes 90 days of launch stabilization and covered-defect correction. After that, you can arrange ongoing care with Calibre or another qualified provider.

A scoped care arrangement can cover monitoring, backup checks, supported dependency updates, security patches, incident triage and reporting. Hosting, third-party services, major upgrades, new features and extended-hours support are considered separately, so the operating budget reflects the coverage you actually need.

See how ongoing costs enter the comparison

Make the switch depend on evidence.

Before cutover, the agreed workflows and integrations must pass, the agreed data must be migrated and reconciled, and representative users must be able to complete their work.

Readiness also includes the agreed performance and security requirements, tested backup and restore procedures, and any parallel running required by the launch plan. Rollback arrangements are defined for the particular system and transition.

The incumbent remains available until agreed readiness is approved. We account for that overlap in the transition plan and cost comparison.

Check your mandatory requirements before a production build.

Security, procurement and operating requirements are part of feasibility. Calibre identifies what your company requires before production development and does not start the build if a mandatory requirement cannot be met.

Agreed security requirements become part of readiness. Actual controls and supplier evidence must be assessed for your scope; no general statement replaces that review.

For information about what to share in an initial inquiry, use the data-handling page.

Read Privacy & Data Handling