Anchor.Social

Anchor your community in your product. Anchor.Social brings branded communities, conversations, and chat into the websites and app screens your customers already use. It is a Zeeker product; Zeeker ID, community access, and the underlying Social and Chat services continue to provide identity and permissions. Start from a custom configuration or one of eight Embed Element presets: Group Chat, MOD Chat, Support Forum, Comments, Reviews, Product Q&A, Community Feed, or Polls.

Elements are not separate mini-products. A preset initializes ordinary controls for canonical Social feeds, post types, threads, composers, chats, identity, and moderation. If an underlying capability is missing, it must be added to Social first or omitted from Embed. Contextual activity can stay attached to a canonical URL or stable host object, while a Connected embed can also participate in the community on zeeker.com.

At a glance

Loader	https://embed.zeeker.com/api/embed/widget/loader.js
oEmbed provider	https://embed.zeeker.com/api/embed/widget/oembed
Configurator	https://embed.zeeker.com
Initial code	~1.7 KB gzip async bootstrap; current ~43.5 KB gzip runtime loaded asynchronously when required by the mode
Browser support	Chrome / Edge / Firefox / Safari ≥ 14, mobile parity
Auth model	Connected or deployment-supported Embed only · public or authenticated reads · read-only or authenticated participation · Zeeker login or community SSO
Theming	Per-embed auto, light, or dark + background, generic border/top-header, accent, radius, and font controls
Cost during beta	Free

Quick install

<!-- Drop this anywhere on your page -->
<script
  src="https://embed.zeeker.com/api/embed/widget/loader.js"
  data-zeeker-config="YOUR_CONFIG_ID"
  async
></script>

Get a YOUR_CONFIG_ID from the Anchor.Social dashboard. Create a community there or select one you already administer; shared community settings remain available in Admin Center. The community supplies the capability ceiling; the published config selects the subset, presentation, connection, and identity policy. Host markup cannot widen either.

Host-triggered integrations use the interaction-first trigger.js entry point, which waits for the configured button or link before downloading the runtime.

Canonical public Embed marketing and demo pages advertise the JSON oEmbed provider in their document head. The provider accepts only the fixed public route catalog, clamps requested dimensions, returns cacheable CORS-readable JSON, and renders through a dedicated sandboxed player. The provider and player always send noindex; authenticated, configurator, claim, stats, and unknown URLs are never valid oEmbed targets.

Why teams add it

• Focused canonical Social: install an allowed subset of existing reviews, questions, comments, chat, feeds, or polls without inventing an Embed-only implementation.
• Context across web and mobile: map the same stable article, product, event, or app object from a website, native SDK, or WebView.
• Per-embed presentation and policy: narrow content and outside access; choose headers, border, scroll/loading, composer placement, Connected behavior, viewing, participation, login timing, and theme. SSO provider setup remains community-level.
• Low adoption cost: paste the loader or use the iOS/Android integration generated in Deploy.

Current policy boundary

Connected embeds, public/authenticated viewing, read-only/authenticated participation, and the documented login modes are enforced end to end. Embed-only configs are also supported when the deployment reports the complete isolation capability.

Embed only creates an exact config-owned content partition. It does not expose that content in ordinary Social feeds, search, profiles, notifications, SEO, or shared Social analytics, and it does not share content with another embed-only config in the same community. The runtime receives only a short-lived scope for that config; a config edit, pause, unpublish, or mode change invalidates old scope on the next request. Scoped Chat additionally rechecks current membership, role, feature switches, publication state, and revision.

The capability is fail-closed. If the server cannot verify the required exact-config database, authorization, revocation, or signing boundary, the dashboard reports Embed only or named guests as unavailable and the backend refuses to publish or boot it—never silently converting it to Connected or canonical Social/Chat storage. Guest-enabled surfaces retain login/signup and add a display-name-based guest choice. See Connection and identity policy.

If you need the detailed surface area, the pages below cover installation, modes, theming, SSO, events and moderation.

Next steps

• Embed Elements — all eight authoring presets, capability boundaries, web/mobile placement, policy, previews, and public demos
• Installation — supported web, native app, WebView, SPA, and CMS patterns
• Container modes — the four Element placements and their underlying floating, fixed, anchor, pill, and trigger containers
• Theming — match your brand with data-zeeker-* attributes
• Configurator — the no-code GUI for tuning a config
• SSO — sign your users in automatically with a JWT
• JavaScript API — window.zeeker.open(), identify(), events
• Events — what window.zeeker.on(…) emits
• Moderation & abuse
• Performance & caching
• Troubleshooting

Find your product fit

• Ecommerce — product questions, reviews, and customer communities.
• News and publishing — article conversations and reader communities.
• Apps and platforms — member discussions, shared progress, and support inside your product.

The Anchor.Social rebrand keeps existing Widget IDs, data-zeeker-* attributes, window.zeeker, SDK names, API routes, and installation URLs compatible. Customer-selected brands and explicit Zeeker network and identity settings remain authoritative.