Pilot and support
Registry Stack’s core components are open source under Apache-2.0. A government or its chosen partner can deploy them without a license fee. Aubex offers paid help when a team wants support designing, connecting, deploying, or operating the system.
Open-source software and paid services
Free and open source
Open-source availability does not include a support response time or delivery team.
Paid help
Scope and pricing are agreed against the source systems, deployment environment, training needs, and support level. A software license purchase is not required.
Discuss the scope →Paid services
A government can choose the services it needs without buying a software license.
Choose one registry, one public or partner service, and the first questions or fields worth testing.
Connect the existing file, database, or registry system and configure the read-only access Registry Stack needs.
Deploy on infrastructure chosen by the government, configure operational controls, and prepare the service for handover.
Work with the registry owner to agree what can be asked and returned, then configure signed answers or agreed fields.
Train the government team and its implementation partner to operate, inspect, and extend the deployment.
Plan version upgrades, troubleshoot production issues, and maintain an agreed support arrangement.
A practical first pilot
A pilot should be small enough to understand and complete, but real enough for the registry owner and service team to evaluate.
Name the registry owner, the public or partner service, and whether it needs one signed answer or selected data.
Use synthetic data to test the source connection, request rules, result, errors, and audit record with the responsible teams.
Connect the real source read-only, test the agreed questions or fields, document the deployment, and train the operating team.
Planning a pilot
Review the software