GLACIER and ATRIUM aren't separate silos — they're built on the same identity foundation, and that's what makes them work together.
The connection is UIID's key-value storage. Both GLACIER-built mini apps and ATRIUM networks can read and write structured data directly onto a user's UIID — either their Core ID or a specific alias — instead of each maintaining a separate database of the same person's information.
What this means in practice: a mini app you build in GLACIER — a booking tool, a private wiki, a simple dashboard — can recognize a member of your ATRIUM community through the same alias they already use to sign in there, without you exporting a member list or wiring up a second login system.
Why this matters for growing communities: as your ATRIUM network matures, you'll eventually want something ATRIUM doesn't ship out of the box — a custom booking form, an internal tool, a members-only calculator. GLACIER lets you describe it in plain language and deploy it on Web4 infrastructure, already speaking the same identity language as the network it's extending.
Where to start: build your community at web4.community, then build the tool that extends it at glacier.linkspreed.com. Both are signed in with the same UIID.