Good question - we (Infoxchange) have had a large database of providers centred around services for disadvantaged and at risk people in Australia since the early 90s, it goes back so far that we used to offer this information up over BBS - and we actually ran the very first &#x27;online&#x27; search engine in Australasia, back then I think it was actually called &#x27;the info X change&#x27; or something quite corny like that but hey - it was the 90s!<p>I gave a talk on the history and journey with search and our database of providers back in 2014 - those slides are still very much relevant and contain some screenshots from the mid 90s of someone accessing the data via mosaic - check out: <a href="https:&#x2F;&#x2F;smcleod.net&#x2F;search-a-journey-of-delivery-on-a-budget&#x2F;" rel="nofollow">https:&#x2F;&#x2F;smcleod.net&#x2F;search-a-journey-of-delivery-on-a-budget...</a><p>With regards to AskIzzy, it&#x27;s essentially a front end that accessed data from our services &amp; providers database which is called &#x27;Infoxchange service seeker&#x27;, that platform is a number of Python app that use Elasticsearch backed by PostgreSQL with PostGIS, it has its own set of front ends for various purposes and has a pretty flexible API to query data, which is what is used by things like AskIzzy to get the information they need.<p>With regards to updating data - that is obviously the hardest part, we all know garbage in = garbage out, so we tend not to like the idea of scraping or anything like that. Many service providers do not have the technical skills or infrastructure to expose the the state of their services online but are more than happy to fill out a small status update form on a website, email an update to one of our systems etc... We also have a dedicated team of database updaters that make regular stop ins with service providers to ensure their details are correct.<p>I should also mention that we are 100% non-profit, charitable organisation - so we&#x27;re not making any money off AskIzzy or any other platform &#x2F; service we run and were very transparent about that.<p>* sorry for any typos - wrote this reply on my phone