The delivery package
Once you have validated your application on Shared Dev, you submit a standardised set of technical artifacts. Production onboarding is built from this package, and an incomplete one is the most common reason onboarding stalls after a successful integration.
A populated Git repository
Contains everything needed to create an instance of your application, and names the immutable release tag or target branch to be deployed to production. It includes:
ci.yml— a fully tested Landscape blueprint. If you maintain several execution profiles, state explicitly which one production runs.provider.yml— the configuration registering your application with the platform's unified Managed Services interface.
A static build ID
A unique, deterministic build identifier — a Git commit hash or release tag — so that builds are reproducible across environments.
Technical and API documentation
Your application architecture, API specifications, the versioning standard you follow (SemVer), and a change log describing what changed in each release.
A database schema migration strategy
Documented procedures for how schema migrations, updates and backward compatibility are handled when a version is upgraded.
Customer Portal metadata
Product descriptions, branding assets, the configuration inputs a customer has to supply, and support contact details for the listing. The Customer Portal API also takes your license models, prices and resource models for deployment.
Update and lifecycle documentation
How your application is maintained over its life on the platform. Four things need to be written down:
- Supported versions — which releases you support, for example the latest N versions, following semantic versioning.
- How updates start — whether updates are customer-initiated or vendor-managed, and how you communicate that a version is available and ready to upgrade to.
- Hotfixes and security patches — your SLA timelines and deployment procedure for critical security fixes, stated separately from routine feature releases.
- Database migrations — the operational workflow for non-breaking schema updates, and how data is rolled back if an upgrade fails.
Commercial and organisational prerequisites
The package is not complete on its technical artifacts alone. These must be in place as well:
- A contract between you and GovTech Platforms, signed and in force.
- Named contact persons on your side for technical, commercial and security matters.
- The agreed support channel, reachable and staffed for the service levels you carry.