Municipal websites
Estimate traffic, published documents, search and content-management requirements. Include the staff workflow for publishing service information.
Choose infrastructure around the public website or departmental application your city, municipality or county needs to operate.
Estimate traffic, published documents, search and content-management requirements. Include the staff workflow for publishing service information.
Record form, database and notification dependencies. Define how residents receive confirmation and how staff review and update a request.
Size storage and processing for the files or datasets the application publishes. Confirm supported formats and any specialist software requirements.
Assign application owners, editor roles and support responsibilities. Record approved hosting locations and the documentation required by your purchasing process.
Compare the application’s CPU, RAM and storage requirements with the available plans. A document website and an interactive service-request system may need different resources. Include licences, backups and administration in the operating budget, then confirm the selected location and final configuration.
Use the server comparison to review the two server types, or explore country and city guides for location options.
Use test information to find a service, submit a sample request and verify its confirmation and staff workflow.
Check publishing permissions, mobile use and the process for correcting or withdrawing an outdated notice.
Restore the website or application and document who verifies records and resumes its operation.
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.