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 |
| Available | SendGrid delivery with SPF/DKIM/DMARC domain authentication | |
| In-app | Available | Real-time in-product messages — no external provider to configure (Growth and Agency plans) |
| SMS | Beta | Twilio-compatible API with your account and numbers |
| Beta | Approved-template enforcement, template catalog sync |
Beta means the integration is code-complete and exercised against provider-grade test infrastructure, with live carrier verification still in progress. We label it honestly so you never find out mid-campaign.
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.
Next steps
- Read the core concepts — five minutes, and the rest of the docs will make sense.
- Pick an SDK quickstart above and send yourself a test message.
- Invite your team — roles and permissions cover marketers, developers, and analysts.