Introduction

Welcome to the Hober documentation.

Hober is a customer-messaging platform for product and growth teams: one composer, one audience model, and one set of delivery controls across every channel your users are on.

Channels

Channel	Status	Notes
iOS push	Available	APNs delivery with your app credentials, native SDK
Android push	Available	FCM delivery with your app credentials, native SDK
Web push	Available	Browser SDK with permission and token handling
Email	Available	SendGrid delivery with SPF/DKIM/DMARC domain authentication
In-app	Available	Real-time in-product messages — no external provider to configure; included on every plan
SMS	Available	Twilio-compatible API with your account and numbers
WhatsApp	Available	Approved-template enforcement, template catalog sync

What you can send

• Notifications — one-off or scheduled messages, with per-channel content, A/B variants, and templates.
• Campaigns — multi-message send containers with per-message reports.
• Journeys — event- and segment-triggered automation flows with waits, branches, and entry/exit rules.
• Recurring sends — preset schedules with timezone-safe delivery.
• In-app experiences — cards and fullscreen messages targeted by screen and behavior; see the in-app guide.

Targeting and controls

• Subscribers, lists, and behavioral segments — filter on attributes and tracked events; see segments and audience filters.
• Events — track behavior from the client SDKs or your backend via server-side event tracking.
• Delivery guardrails — consent, quiet hours, and frequency caps are enforced on every send, including sends proposed by an AI agent.
• Measurement — per-channel delivery and engagement analytics, holdout groups with lift readouts, and A/B testing.

Ways to integrate

• Client SDKs — Browser, React Native, iOS, and Android.
• Server SDKs — Go, Node.js, Python, and Java for event tracking from your backend; sends go through the REST API.
• REST API — everything the dashboard does; start with the API reference.
• Integrations — Segment, Shopify, Zapier, Mixpanel, Amplitude, Slack, and more; see the integrations overview.
• AI agents — an MCP server with human-in-the-loop approvals; see agent access.

Switching from another platform? See the migration guides for Braze and Klaviyo.

For AI coding assistants

Integrating with an AI assistant (Claude Code, Cursor, Copilot, …)? Point it at:

• /llms.txt — a machine-readable index of every page here; /llms-full.txt inlines the full documentation in one fetch. Hober is newer than most models' training data — an assistant that fetches these integrates against the real API instead of a guessed one.
• The integration skill — skills/hober-integration encodes the integration procedure (platform decision tree, install → initialize → verify loops, key-security rules) for skill-consuming assistants. Copy it into .claude/skills/ (Claude Code) or zip-upload it (claude.ai). Its sibling skills/hober covers operating Hober through the MCP server once you're integrated.

Next steps

1. Read the core concepts — five minutes, and the rest of the docs will make sense.
2. Pick an SDK quickstart above and send yourself a test message.
3. Invite your team — roles and permissions cover marketers, developers, and analysts.