Prototype · Australia-focused

Decide on a suburb with official data and clear context—not guesswork.

One payment unlocks a structured briefing that combines police-recorded offences, mapped infrastructure, and (where available) public community chatter—summarised so you can act confidently.

  • Live Brisbane district aggregates from Queensland Open Data (when `/api/qld-crime` resolves)
  • Radial score · KPI tiles · donut + bar offence mix widgets
  • Illustrative map, sentiment, and PDF scaffolding for the paid product arc

Report generator

Enter a suburb or postcode. Metrics auto-map to a QPS police district (North or South Brisbane in this build). Map and narrative stay illustrative.

Recently viewed (demo):
Stripe-ready checkout PDF export layout No login required

Payment & delivery

Production build wires a Stripe Payment Link or Checkout Session. Email capture precedes PDF delivery and receipt.

Powered by Stripe · simulation

What you receive

Four coordinated views mirror the downloadable PDF narrative: map context, verified stats, qualitative signals, then infrastructure grounding.

Crime geography

Heat-informed map framing with policing and transit anchors.

Official breakdown

Category totals, trend direction, analyst-style callouts.

Community digest

Topic bullets extracted from noisy public chatter (planned integration).

Infrastructure roster

Schools, stations, beats—proximity-aware copy for purchasers.

Target overview

Briefing dashboard

Overall risk rating Moderate 12-month trend stabilising
Connecting to metrics…

District stability visual score

/ 100
Latest period QPS CSV month label
District total Aggregate pillars*
vs prior year month YoY benchmark
vs 12-month district avg Same district window

Category mix · latest CSV month

Crime heatmap overview

Incident emphasis layer (demo). Uses OpenStreetMap—replace with Maps Platform in production.

Inset context: Brisbane metro · scroll to zoom · drag to pan

Official police statistics

Recorded incidents · latest CSV month · district aggregate

Community sentiment

AI-analysed · placeholder summaries for prototype

Powered by LLM-ready pipeline

    Community vigilance score

    Local infrastructure

    Mirrors supplementary map plotted in the PDF appendix.

      Downloaded PDF — layout preview

      Portrait A4-ready styling. Export is simulated here; integrate WeasyPrint, ReportLab, or headless Chromium in backend.

      Executive summary

      Risk rating
      12-month trend
      Primary category

      Official data · category table

      Category Incidents

      Community sentiment highlights

        Composite signal

        Infrastructure & proximity

          Suburban Safety Report © · Provided as-is using public references and illustrative analytics. Not financial or conveyancing advice.

          Simple pricing

          AUD $9.95 per briefing

          Covers compilation, visuals, PDF packaging, and email delivery path. Taxes additional if applicable.

          Typical Stripe fee
          Approx. ~1.75% + $0.30 per successful charge · verify current pricing.
          Refund posture
          Implement a postcode coverage lookup before Checkout to minimise disputes.

          Lean operations

          Indicative monthly run costs

          Targets a micro-SaaS where low fixed infra matters more than squeezing marginal latency. Figures are illustrative—revise quarterly.

          Infrastructure

          AUD $8–22

          Entry unmanaged VPS · scale after consistent volume.

          Maps APIs

          Often $0

          Credits may cover Places + Maps if traffic stays modest.

          Open police data

          AUD $0

          Licence-checked extracts ingested nightly or weekly.

          Community feeds

          AUD $0–120+

          Hosted scrapers/residential proxies spike costs—design graceful degradation first.

          LLM parsing

          < AUD $15

          Lightweight models per report batches stay cheap versus revenue at $9.95 each.

          Marginal breakeven

          < 5 reports/mo*

          *Assuming lean stack and minimal paid enrichment. Tune after real usage records.

          Production pipeline

          Official data sources & APIs

          Mixed view: live QPS district CSV metrics (where the API succeeds) plus illustrative suburb context, sentiment, and maps. Always follow each upstream licence and attribution rule.

          1. Queensland crime statistics (QPS / Open Data)

          Monthly reported offence counts and rates by crime type and geographic area are published on the Queensland Open Data Portal. Use bulk CSV for a local warehouse, or the portal’s CKAN API for programmatic discovery and resource URLs.

          QPS Online Crime Map (reference)

          Use the official map to align product language with QPS offence groupings (e.g. Unlawful Entry, Property Damage, Assault)—not as a scrape target. Locations are approximate; read the map’s own limitations and disclaimers.

          2. Live district stats on this prototype

          Charts can call Cloudflare Pages Function  GET /api/qld-crime?district=… (South Brisbane mapped to CBD / inner-east demos · North Brisbane to northern corridors like Albany Creek) for CSV-backed monthly aggregates sourced from Queensland Open Data — edge-cached briefly to protect the origin budget.

          3. Infrastructure, places & schools

          Combine Google’s Places APIs for live points of interest (police, stations, retail hubs) with Queensland’s official school location products where you need department-verified coordinates or catchment context.

          Google Maps Platform — Places

          Suitable for nearest police stations, rail stations, shopping centres, and other place types around a searched suburb or geocode—subject to Google’s terms and billing.

          Queensland state schools (Open Data)

          Official state school geographic products and related education datasets on the portal—use for authoritative coordinates and catchments instead of, or alongside, Google results.

          Support & data integrity

          Production version should disclose refresh cadence, licensing, and omit social module when upstream fails rather than silently degrading QA.