public mission begins
2004Public hotspot listings across Estonia.
HAAM B2B · Public digital infrastructure
WiFi.ee
I started with a public Wi-Fi map. Today WiFi.ee connects hotspot search, quality data and venue-admin tools.
WiFi.eeVisitorsVenuesCommunityOperators
One public recordDifferent needs · Shared responsibility
audiences in one service
4Visitors, venues, contributors and operators.
quality signals
5Security, speed, Wi-Fi generation, power, workspace.
living public record
1One shared hotspot record.
In brief
Evidence JSON ↗- Role
- Started the public map at 13; built the newer venue-admin tools in 2026.
- Shipped
- Maps, hotspot listings, claim approvals, roles and publishing states.WiFi.ee ↗
The responsibility
Keep the old records. Build the new service.
Old hotspot records and links had to survive the move to a new map and operator tools.
One platform, four perspectives
The product changes depending on who arrives.
01
People looking for a connection
Location, access, safety and working conditions.
02
Venues responsible for the experience
Claim and update a venue's hotspot listing.
03
A community keeping the map alive
Suggest new places, edits and speed measurements.
04
The people maintaining public trust
Review changes, evidence and publishing history.
Design decisions
Claims, reviews and corrections.
01
Service model
A hotspot needs a record and an owner.
Each hotspot has a page with owners, history and quality data.
- Every location can hold structured technical and visitor information
- Edit history and contributor activity make maintenance visible
- Venue claiming connects public records with responsible operators
02
Trust model
Show network quality.
The quality score combines security, network speed and working conditions.
- Security carries the largest share of the score
- Speed and Wi-Fi generation show practical network capability
- Power, quietness, comfort, and lighting acknowledge the real use context
03
Information architecture
One record, several views.
Hotspot, city and country views use the same records.
- Search and maps help people find nearby options
- City and country pages make coverage and quality comparable
- Admin and community tools feed improvements back into the public surface
04
Legacy modernization
Keep the archive.
The rebuild kept old hotspot records and links.
- Long-lived hotspot records remain discoverable
- Normalized data supports maps, statistics, search, and APIs
- The new stack can evolve without discarding the civic memory already collected
Connected architecture
A service that can keep growing after the redesign.
Public experience
Next.js
Maps, search, directories and hotspot pages.
Shared data
Postgres + PostGIS
Hotspot records, geo queries and scores.
Operations
Directus
Edit records, review changes, manage media.
Media and delivery
Cloudflare R2
Images and public media assets.
What the platform now connects
The running service.
01A searchable public map and database built around individual hotspot pages
02Country and city directories that expose coverage, speed, and quality patterns
03A quality score that connects network security with real working conditions
04Venue claiming and administrative workflows for the organisations responsible
05Community contributions, activity, favourites, check-ins, and discussion
06A shared platform direction across the website, operator tools, and mobile apps