Public portals
Estimate concurrent usage, account activity and document access. Identify periods when applications are expected to receive unusually high demand.
Build a hosting brief for public portals and departmental applications, with clear ownership across the agencies and services they depend on.
Estimate concurrent usage, account activity and document access. Identify periods when applications are expected to receive unusually high demand.
Record supported software, database requirements and scheduled processing. Identify the team responsible for each application component.
Map interagency connections, identity systems and data exchange. Document update frequency and the effect of an unavailable dependency.
Confirm approved locations and the service evidence required by your agency. Assign administrator access, maintenance, monitoring and recovery responsibilities.
Use the workload measurements and approved operating requirements to compare dedicated and cloud plans. Review database memory, storage performance and capacity alongside processor allocation. Confirm the service scope and required documentation before selecting infrastructure for a production application.
Use the server comparison to review the two server types, or explore country and city guides for location options.
Use test accounts and records to validate sign-in, application steps, documents and notifications across the dependent services.
Test the expected load and document how the team will respond to capacity limits or a failed dependency.
Set the service restart order and confirm which team checks each application and data connection after restoration.
The standard dedicated and cloud plans are presented as unmanaged. Assign responsibility for the operating system, applications, updates, monitoring and backups. Review server management responsibilities and use the deployment checklist to plan the move.
Compare the current configurations and prices, then review your product, location, options and final total in the cart.