It started as a way to help us publish geospatial data. It quickly morphed to something quite different. You can call it scope creep. And despite this term being close to a swear word in ICT, it turned out to be very good thing. And that's because while still serving its main purpose, which is to provide an out-of-the-box web based mapping app with all the trimmings (navigation, measure, layer control and search tools), EVRYMAP also: - Provides client-side editing tools - Provides a modular design that allows you to implement custom business logic by simply writing your own apis. EVRYMAP will consume these APIs automatically by defining them in configuration as 'modules' - Implements 1-n relationships between your spatial data and other related data. Which may come from the same or external databases - Can be run as standalone or within an iframe to spatially enable third party applications (and provides the communication mechanism) Using EVRYMAP at the core, we have also deployed a few systems in production environments as commercial apps, namely: -Landify, a mini-cadastre for organizations with a real-estate portfolio. It allows users to easily review, catalogue, and manage real estate data (land parcels and buildings). -MapTheYA, a map-based information system for the management of water networks including topology checks. -Building permits/Expropriations Management Examples of not "map-first" systems, meaning that while the bulk of their functionality are text/form based (applying for electronic copies of documents) they also include embedded maps to improve user experience. This presentation will provide a brief introduction to EVRYMAP, the way it works, how you can configure and extend its functionality and what we plan for the future. And being the new kid on the block, ask the community for input and feedback!