reputecast

module
v1.0.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Oct 24, 2026 License: AGPL-3.0

README

Open source · self-hosted · sends through your own Amazon SES, Postmark, Mailgun, SendGrid, Resend, Postal or any SMTP server

CI


ReputeCast is a newsletter and email-marketing platform you run yourself. It sends through the sending provider you already trust — and it is the only newsletter tool that checks whether your mail will reach the inbox before you send, then guards your sender reputation while it sends, whichever provider delivers it.

It is built by HostRepute, the email-reputation monitoring service, and it works with or without a HostRepute account. Every feature is free. There is no paid edition, no seat limit, no workspace limit and nothing behind an upgrade prompt.

Contents

Features

Know before you send — Send Readiness. Every campaign gets a pre-send check with a verdict (Ready, Ready with warnings, Blocked), evidence and a fix for each finding:

  • sender reputation: domain and IP blocklists (80+ sources with HostRepute), and the bounce and complaint rates of every provider in the route against that provider's own limits (for example the Amazon SES review thresholds);
  • authentication: SPF, DKIM, DMARC, return-path / MAIL FROM and BIMI, checked against the records your provider needs;
  • content: spam triggers, image-to-text ratio, Gmail's 102 KB clipping limit, alt text, plain-text part;
  • links: broken links and links on URI blocklists;
  • compliance: one-click unsubscribe (RFC 8058), footer address, Gmail/Yahoo bulk-sender rules;
  • audience quality: unengaged, recently bounced and role addresses;
  • routing: a healthy provider for every stream, provider terms that allow bulk marketing, no double tracking;
  • estimates: cost per provider, send duration from each provider's rate limit, throttling per mailbox provider.

Guarded sending. Live progress with delivered, bounced, complained, opened and clicked counts per mailbox provider (Gmail, Outlook, Yahoo, iCloud…) and per sending provider. When bounces or complaints cross your thresholds the send pauses — the whole campaign or just one route — and ReputeCast explains what tripped and offers resume, adjust, fail over or cancel. Provider outages are handled the same way.

Bring your own providers, several at once. Built-in adapters for Amazon SES, Mailgun, SendGrid, Postmark, Resend, SparkPost, Mailjet, Brevo, Azure Communication Services, self-hosted Postal and any SMTP server, plus an adapter SDK and a generic HTTP adapter.

  • Capability badges: bulk marketing allowed by the provider's terms, webhooks, domain setup by API, suppression sync, batching, dedicated IPs, sandbox, quota discovery, pricing.
  • One event model: every provider's events (delivered, deferred, hard/soft bounce, complaint, rejected) map to one taxonomy that keeps the provider's original code. Providers without webhooks report through a bounce mailbox.
  • One suppression list shared by every provider: a bounce at one provider stops mail to that address everywhere.
  • Routing per stream (Broadcasts, Automations, System), per list or sender domain and per recipient mailbox provider, with weighted splits (90/10) for migrations and warm-up, and a route tester.
  • Failover: automatic for System and Automations; Broadcasts pause and ask by default, or fail over only to a warmed-up provider.
  • Warm-up planner for a new provider or dedicated IP: daily ramp, most-engaged first, automatic slowdown when bounces rise.
  • Health per provider: status, quota and rate, webhook freshness, error rate and cost.

Provider onboarding in about ten minutes. Pick a provider, connect it (SES through CloudFormation or IAM keys, with SNS topics and configuration sets created for you, sandbox detection and a guided production-access request; API key for API providers; server URL and key for Postal; host, port, TLS, credentials and bounce mailbox for SMTP), verify DNS records live, watch a test message arrive and assign the provider to streams.

Composer. A drag-and-drop email builder on GrapesJS with MJML, wrapped in ReputeCast's own interface: blocks, layers, MJML-aware styles, personalization with Liquid and fallbacks ({{ first_name | default: "there" }}), MJML code view, device, email-client and dark-mode previews, an inbox preview, A/B variants for subject, content and send time, inline deliverability warnings, templates, saved sections, autosave and version history.

Honest analytics. Human opens separated from machine opens (Apple Mail Privacy Protection), a click map on the email, bounces by type with each provider's original diagnostic code, complaints and unsubscribe reasons, results per mailbox provider and per sending provider side by side, A/B results with confidence, export and read-only share links.

Audience. Contacts with saved views, filters and bulk actions; profiles with custom fields, per-list consent history and an activity timeline that shows which provider delivered each email; a segment builder with AND/OR groups, a live count and the generated SQL (and read-only SQL segments for power users); list health with engagement tiers and a sunset policy.

Migration that keeps consent. Import from Brevo, Mailchimp, MailerLite, listmonk, Keila, CSV or XLSX. Unsubscribed, bounced and complained contacts become suppressions and are never re-subscribed; existing suppressions can be pulled from your providers.

Automations. Visual flows on React Flow: triggers (joined a list, form submitted, tag added, API event, date field), delays, emails, branches, filters, A/B splits, webhooks, list actions and goals, with live stats per step, draft/live/paused lifecycle and a version diff before publishing.

Forms and public pages. Embedded, popup and hosted signup forms with double opt-in and spam protection; publisher-branded subscribe, confirmation, preference-center (lists, frequency, pause) and unsubscribe ("fewer emails" option) pages; a public newsletter archive with RSS.

Deliverability. Health per sending domain and dedicated IP, account health per provider, blocklist status, DMARC report summaries and an incident timeline. Connect HostRepute to add 80+ blocklists with delisting requests, Google Postmaster Tools and Microsoft SNDS data; the built-in checks work without it.

Teams, access and approvals. Unlimited workspaces; members with built-in or custom roles and 30+ granular permissions (sensitive ones are flagged and require two-factor); scopes such as "Editor, Beta Program list only"; send approvals for large or risky sends with a snapshot that is invalidated when anything changes; passwords, passkeys, TOTP with recovery codes, Google/Microsoft/GitHub sign-in and OIDC single sign-on (Google Workspace, Microsoft Entra ID, Okta, Keycloak, Authentik) with just-in-time accounts, group-to-role mapping and domain enforcement; an immutable audit log; an instance admin area. Nobody can grant a permission they don't hold — not to a role, a member, an API key or an AI agent.

Quick start

You need Docker with Compose. One command starts Postgres and ReputeCast:

curl -fsSL https://raw.githubusercontent.com/hostrepute/reputecast/main/deploy/docker-compose.yml -o docker-compose.yml
REPUTECAST_ADMIN_EMAIL=you@company.com docker compose up -d

Then read the first Owner's temporary password from the logs and open http://localhost:8080:

docker compose logs app | grep -A4 "ReputeCast is installed"

At first sign-in you replace the temporary password, add a passkey or an authenticator app, save your recovery codes, confirm the public URL and create your first workspace; then ReputeCast walks you through connecting a sending provider.

Images are published to ghcr.io/hostrepute/reputecast with each release. To run your own build instead (or before the first release), build the image from a checkout and point the compose file at it:

make docker VERSION=local
REPUTECAST_IMAGE=reputecast REPUTECAST_VERSION=local REPUTECAST_ADMIN_EMAIL=you@company.com \
  docker compose -f deploy/docker-compose.yml up -d

Want to look around first? make dev && make seed (see Development) loads the Acme demo instance used throughout the design.

Installing without Docker

ReputeCast is a single static binary (Linux, macOS, Windows; amd64 and arm64) that embeds the web app and its migrations. Download it from the releases, point it at Postgres 16, 17 or 18 and run:

export REPUTECAST_DATABASE__URL=postgres://reputecast:secret@localhost:5432/reputecast?sslmode=disable
export REPUTECAST_HTTP__PUBLIC_URL=https://news.example.com
reputecast install --email you@company.com --name "Your Name"   # migrates and creates the first Owner
reputecast serve
Command What it does
reputecast serve Runs the web app, API, webhook ingest and workers. --role=web,worker,ingest splits them across processes. --auto-migrate, --auto-install for containers.
reputecast worker Runs only background jobs (same as serve --role=worker).
reputecast install Applies migrations and creates the first Owner (instance admin with break-glass sign-in).
reputecast migrate up|down|status Manages the schema.
reputecast user reset-password --email … Prints a one-time reset link — works before any sending provider exists.
reputecast user reset-2fa --email … --reason … Removes the authenticator app; the reason goes to the audit log.
reputecast user make-admin|unlock --email … Instance admin flag, clear a sign-in lockout.
reputecast secrets generate-key Prints a new encryption key.
reputecast adapter install|set-url|secret|check|list|remove Installs a community adapter from its manifest, tells ReputeCast where its process runs and issues its signing secret (docs/adapters.md).
reputecast openapi [--yaml] Prints the OpenAPI 3.1 document.
reputecast seed Loads the Acme demo data (development only).
reputecast demo send "<campaign>" [--scenario …] [--elapsed …] [--reset] Sends a demo campaign through the simulated providers so the live monitor moves (development only; see Live sending in the demo).
reputecast version Prints the version.

Configuration

Settings come from defaults, an optional YAML file (--config or REPUTECAST_CONFIG), environment variables and flags, in that order. Environment variables use the REPUTECAST_ prefix and a double underscore between levels (http.public_url → REPUTECAST_HTTP__PUBLIC_URL).

Setting Default Notes
REPUTECAST_DATABASE__URL (or DATABASE_URL) postgres://reputecast:reputecast@localhost:5432/reputecast?sslmode=disable Postgres 16–18.
REPUTECAST_DATABASE__MAX_CONNS 20 Pool size per process.
REPUTECAST_HTTP__ADDR :8080 Listen address.
REPUTECAST_HTTP__PUBLIC_URL http://localhost:8080 The address people and providers reach. Used for webhooks, SSO redirects, passkeys, public pages and links in emails. Use https:// in production. An address saved in Instance admin › Instance & updates replaces it for links, pages and webhooks (moving provider webhooks with it); HTTPS-only cookies and HSTS follow this setting, so keep the two the same.
REPUTECAST_HTTP__TRUSTED_PROXIES — Comma-separated CIDRs or IPs of your reverse proxies; only then is X-Forwarded-For trusted.
REPUTECAST_HTTP__RATE_LIMIT_AUTH 30 Sign-in requests per minute per client IP (on top of per-email lockout).
REPUTECAST_HTTP__RATE_LIMIT_API 600 API requests per minute per API key (per IP for browser sessions).
REPUTECAST_SECRETS__KEY — Base64 32-byte key that encrypts provider credentials, OIDC secrets and TOTP seeds. If unset, REPUTECAST_SECRETS__KEY_FILE is used.
REPUTECAST_SECRETS__KEY_FILE data/secret.key (/var/lib/reputecast/secret.key in Docker) Created with a fresh key on first start. Back it up with the database; without it, stored credentials can't be decrypted.
REPUTECAST_SECRETS__PREVIOUS_KEYS — Old keys during a rotation (values sealed with them still open).
REPUTECAST_ROLES web,worker,ingest Same as --role.
REPUTECAST_WORKER__CONCURRENCY 50 Concurrent jobs per worker process.
REPUTECAST_LOG__LEVEL / __FORMAT info / text debug…error; json for log shippers.
REPUTECAST_METRICS__ENABLED / __ADDR true / main listener Prometheus metrics at /metrics; set an address to serve them on a separate port.
REPUTECAST_UPDATES__CHECK true Daily check of GitHub releases (only the version number is fetched). Can also be turned off in Instance admin. ReputeCast never sends usage data anywhere.
REPUTECAST_AUTH__COOKIE_SECURE true Secure session cookie (always on when the public URL is https).
REPUTECAST_PROVIDERS__ALLOW_PRIVATE_NETWORKS false Let provider URLs entered in a workspace (a Postal server, a generic HTTP adapter) and community adapters' addresses (a sidecar; plain http:// only there) resolve to loopback or private addresses, for providers on your own network. Cloud metadata and link-local addresses are always refused.
REPUTECAST_WEBHOOKS__ALLOW_PRIVATE_NETWORKS false The same for outgoing webhooks and the audit stream.
REPUTECAST_ADMIN_EMAIL / _NAME / _PASSWORD — Used by install and serve --auto-install. Without a password a temporary one is printed.
REPUTECAST_AUTO_MIGRATE, REPUTECAST_AUTO_INSTALL false Container conveniences (the Docker image enables both).

Sign-in policies (methods, password length, breached-password check, two-factor enforcement and grace period, session lifetime and idle timeout, lockout, SSO and social providers) are managed in Instance admin › Authentication, not in configuration.

Running in production

  • TLS and reverse proxy. Put ReputeCast behind a TLS-terminating proxy (Caddy, nginx, Traefik), set REPUTECAST_HTTP__PUBLIC_URL to the https address and REPUTECAST_HTTP__TRUSTED_PROXIES to the proxy's address. Providers deliver webhooks to <public URL>/hooks/…, so the URL must be reachable from the internet; the first-run setup checks DNS, TLS and reachability for you.
  • Scaling. One process runs everything. For more throughput run several serve --role=web,ingest instances behind the proxy and one or more worker processes; they coordinate through Postgres (River).
  • Backups. Back up Postgres (pg_dump) and the secret key. Restoring needs both.
  • Upgrades. docker compose pull && docker compose up -d (migrations run at start), or replace the binary and run reputecast migrate up. Read the release notes; Instance admin › Version & updates shows what changed.
  • Health. /healthz (liveness) and /readyz (database reachable) for orchestrators; /metrics for Prometheus.
  • Custom domains for public pages. A workspace can serve its subscribe page, preference center, unsubscribe page and archive at the root of its own domain (https://news.acme.io/subscribe). Enter the domain in Forms & public pages › Branding and point it at the server with a CNAME to the public URL's host (A/AAAA records with the same addresses for an apex domain, or the _reputecast.<domain> TXT record shown there); the pages answer on it once the DNS check passes. Give the proxy a certificate for the domain and keep the original Host header: with Caddy's on-demand TLS, set ask http://localhost:8080/p/_/tls-check so certificates are issued only for verified domains. Emails keep linking to the public URL.

How it works

                 ┌──────────────────── reputecast (single binary) ─────────────────────┐
 browser ──https──▶ web role: SPA (embedded) · REST API (Huma, OpenAPI 3.1) · public pages│
 providers ─────▶ ingest role: /hooks/<adapter>/<token> → verify → store raw → 200      │
 AI agents ─────▶ MCP server (permission-checked tools)                                  │
                 │ worker role (River on Postgres): sends, event normalization, sync,    │
                 │   health checks, warm-up, automations, imports, reports, retention    │
                 └──────────────┬───────────────────────────────┬──────────────────────┘
                                │                               │
                           PostgreSQL                 sending providers (adapters:
                    (data, jobs, audit log)            SES, Postmark, Postal, SMTP, …)
  • Providers are plugins. Each adapter implements one contract (internal/providers/provider.go: capabilities, send, parse webhook, plus optional domain setup, webhook registration, quota and suppression sync) and must pass the shared contract-test suite. Core code never imports an adapter. Community adapters run in their own process and are called over a signed protocol, written with the TypeScript SDK in sdk/ (docs/adapters.md).
  • Webhooks are cheap to receive. Ingest verifies the signature, stores the raw payload and answers 200 immediately; a job normalizes events later, so provider retries never pile up.
  • Access control is one check. Every API operation declares the permission it needs (visible as x-permission in the OpenAPI document). Users, API keys and MCP agents all pass the same check in internal/authz; keys and agents can never exceed their creator.
  • Everything that changes something is audited, in the same transaction as the change, with before/after values, actor, IP, user agent and request id. Audit entries are immutable (enforced by a database trigger).
  • The web app (React 19, TanStack Router and Query, Tailwind 4) is built with Vite and embedded in the binary; API types are generated from the OpenAPI document.
  • Adding a provider: docs/adapters.md shows how an adapter is written and contract-tested, and how to map any HTTP API without code.
  • Sends are guarded. Send Readiness runs again as a send starts; a scheduled send it blocks is held, and starts once a recheck passes. A send builds its recipient list in pages, routes each recipient, then hands batches to the providers from River jobs within each provider's rate and each mailbox provider's throttle; every message is claimed before it goes out, so nothing is sent twice. Bounce, complaint and deferral rates are checked every two seconds against the campaign's thresholds, and a rate that is over its limit with enough evidence pauses just the mailbox provider or sending provider it concerns. Opens and clicks come back through /t/o and /t/c, with privacy-proxy and scanner traffic counted apart.

Security

  • Passwords hashed with argon2id; optional breached-password check (k-anonymity, can be turned off for offline installs).
  • Sessions and API keys are random 256-bit tokens; only their SHA-256 hashes are stored. Session cookies are HttpOnly, SameSite=Lax and Secure on https.
  • Two-factor with TOTP, passkeys (WebAuthn) and one-time recovery codes; policies can require it for everyone or for anyone holding a sensitive permission.
  • Identifier-first sign-in with generic errors (no account enumeration), per-email lockout and per-IP rate limits.
  • Provider credentials, OIDC client secrets, HostRepute tokens and TOTP seeds are encrypted with AES-256-GCM bound to their row, are write-only and are never returned by the API. Keys can be rotated.
  • Cross-site request protection (Go's CrossOriginProtection), a strict Content Security Policy, X-Frame-Options: DENY, HSTS on https, and client IPs taken from forwarded headers only behind trusted proxies.
  • User-written SQL segments run in a read-only transaction with a statement timeout, as a role that can only read a per-query view of one workspace's contacts.
  • Outgoing webhooks are signed (HMAC-SHA256) and blocked from private networks.
  • The audit log records allowed and denied actions and cannot be edited from the application.

Found a vulnerability? Please email security@hostrepute.com instead of opening an issue.

API, webhooks and MCP

  • REST API under /api/v1, documented by the OpenAPI 3.1 document at /api/openapi.json (or reputecast openapi). Errors are RFC 9457 problem documents with a stable code, and permission errors name who can help.
  • API keys (Settings › Keys & MCP) carry a subset of your permissions, optionally scoped to lists and with an expiry. Send them as Authorization: Bearer rc_live_…. They are shown once.
  • Outgoing webhooks (Settings › Webhooks) deliver signed events with retries and a delivery log.
  • MCP server for AI agents: create an agent in Settings › Keys & MCP, give it permissions (for example reports and deliverability, or the right to pause a send but never to start one) and point your MCP client at <public URL>/mcp with the agent token. Agents' actions appear in the audit log.

Development

Prerequisites: Go 1.27 (the toolchain downloads automatically), Node 24 LTS with pnpm, Docker.

make deps        # Go modules + web dependencies
make dev         # Postgres + Mailpit (docker compose), API with live reload on :8080, web on :5173
make seed        # load the Acme demo data

Open http://localhost:5173. Demo accounts (password reputecast-demo):

Account Role Notes
linh@acme.io Owner, instance admin Authenticator secret JBSWY3DPEHPK3PXP; recovery code b4xk-9q2m-7hdn
aisha@acme.io Viewer Password only (two-factor grace period)

Mailpit shows every email the demo sends at http://localhost:8025.

Live sending in the demo

The demo's sending providers are simulated: nothing they send leaves the machine. reputecast demo send starts a campaign's send through them as Sofia Rossi, with Marcus Chen's approval recorded, and the running server's worker keeps sending in real time, with deliveries, bounces, complaints, opens and clicks at the rates of the live monitor's designs:

export REPUTECAST_ENV=development   # the command refuses to run otherwise
go run ./cmd/reputecast demo send "Weekly Digest #142" --elapsed 20m
go run ./cmd/reputecast demo send "Weekly Digest #142" --scenario outlook-complaints --elapsed 20m --reset
go run ./cmd/reputecast demo send "Weekly Digest #142" --scenario postal-outage --elapsed 17m --reset

--elapsed starts the send that long ago and fast-forwards it, so the monitor opens mid-send. outlook-complaints makes lapsed Outlook readers complain until the Outlook share auto-pauses; postal-outage makes Postal refuse connections 14 minutes in, so its share is held. --reset clears an earlier send of the campaign, including what it changed elsewhere (provider statistics, suppressions from its bounces). It only runs in a workspace whose providers are all demo providers.

Task Command
All tests (Go unit + integration on real Postgres, web unit tests) make test
Linters (golangci-lint, ESLint, TypeScript) make lint
Regenerate sqlc, OpenAPI and web API types make generate
Production build (web app embedded in bin/reputecast) make build
Docker image make docker
Landing site (reputecast.com): build, or live reload on :5288 make site, make site-dev
Adapter SDK and template: build, test, run through the Go runtime make sdk
Compare a screen with its design board at 1440/834/390 cd web && pnpm shot --path /w/acme-newsletter/campaigns --design Campaigns
Side-by-side QA of boards and screens, with a difference score (scripts/qa-map.ts maps boards to routes) cd web && pnpm qa --only Report,Campaigns
Accessibility sweep of the same screens (axe-core, WCAG 2.0–2.2 A and AA) cd web && pnpm a11y
Re-render the demo's placeholder images cd web && node scripts/demo-images.ts [file.png …]

The screenshot tools read the design boards from http://localhost:8765: python3 -m http.server 8765 -d design/boards serves them. Static boards render as they are; the phone and tablet wrappers and the boards with live parts (composer, automation flow, landing page) also need the design canvas runtime saved as design/boards/support.js, which is not part of this repository.

Integration tests start Postgres 18 with Testcontainers, or reuse the compose database when it runs (make test does that automatically). CI runs the Go suite on Go 1.27 against Postgres 16, 17 and 18. Packages test in parallel against one server; go test -p 4 ./... keeps the connection count within Postgres' default max_connections.

Read docs/dev/CONVENTIONS.md before contributing: it explains how a screen is built from the design boards to the API, the demo data and the tests.

Project layout

cmd/reputecast/        the binary
internal/
  api/                 Huma setup, access rules, errors
  app/                 wiring (domains plug in from wire_<domain>.go)
  authz/ authn/        permissions and roles; passwords, tokens, TOTP
  audit/ secrets/      audit log; encryption at rest
  accounts/ workspaces/ campaigns/ providers/ …   one package per domain
  store/               sqlc queries (queries/*.sql) and generated code
  demo/                the Acme sample data
migrations/            goose SQL migrations (embedded)
web/                   React app (embedded into the binary)
site/                  reputecast.com landing page (static, prerendered)
design/                the design prototype boards and the Clearwater design system
docs/                  specs, roadmap, conventions, design inventory
deploy/                production docker compose and release Dockerfile

Roadmap

See docs/ROADMAP.md for milestones and status, and docs/DESIGN_INVENTORY.md for how every designed screen maps to the spec.

Contributing

Issues and pull requests are welcome.

  • Keep make test, make lint and make build green, and add tests with your change.
  • Follow the design boards for UI and the specs for behaviour.
  • Write commit messages as Conventional Commits, for example fix(sending): … (see docs/dev/CONVENTIONS.md).
  • Never add paywalls or license checks: every feature in this repository is free.

License

ReputeCast is licensed under the GNU Affero General Public License v3.0.

Built by HostRepute.

Directories

Path Synopsis
cmd
reputecast command
Command reputecast is the single ReputeCast binary: the web app and API, background workers, webhook ingest, installation and maintenance commands.
Command reputecast is the single ReputeCast binary: the web app and API, background workers, webhook ingest, installation and maintenance commands.
internal
access
Package access holds the presentation side of authorization shared by the team, roles, API key and MCP screens: the permission catalogue as the API returns it, scope labels ("Beta Program list only"), sign-in method and two-factor labels, and the "who can help" helper names.
Package access holds the presentation side of authorization shared by the team, roles, API key and MCP screens: the permission catalogue as the API returns it, scope labels ("Beta Program list only"), sign-in method and two-factor labels, and the "who can help" helper names.
accessrequests
Package accessrequests backs the "Request Editor access" action on the 403 screen: it names the smallest built-in role that grants a missing permission and sends the request to the members who manage the team.
Package accessrequests backs the "Request Editor access" action on the 403 screen: it names the smallest built-in role that grants a missing permission and sends the request to the members who manage the team.
accounts
Package accounts implements sign-in (identifier first, password, passkeys, two-factor, recovery codes), sessions, password resets, accepting invitations, the signed-in person's profile and security settings, and the first sign-in setup of an instance.
Package accounts implements sign-in (identifier first, password, passkeys, two-factor, recovery codes), sessions, password resets, accepting invitations, the signed-in person's profile and security settings, and the first sign-in setup of an instance.
api
Package api holds the Huma (OpenAPI 3.1) setup shared by every domain: operation helpers that declare the required permission, the middleware that authenticates users, API keys and MCP agents and authorizes them with internal/authz, and RFC 9457 error helpers.
Package api holds the Huma (OpenAPI 3.1) setup shared by every domain: operation helpers that declare the required permission, the middleware that authenticates users, API keys and MCP agents and authorizes them with internal/authz, and RFC 9457 error helpers.
apikeys
Package apikeys manages API keys and MCP agents (A5 §3.9, §5.13).
Package apikeys manages API keys and MCP agents (A5 §3.9, §5.13).
app
Package app wires configuration, the database, background jobs, the HTTP API and every domain package into one runnable process.
Package app wires configuration, the database, background jobs, the HTTP API and every domain package into one runnable process.
approvals
Package approvals implements send approvals (add-on 3.8, 5.12) and the Review & send flow around them (spec 7.5): the workspace policy and its rules, approval requests with a snapshot of what they cover (content and subject, audience definition, route, schedule), invalidation with the exact diff when any of it changes or the audience moves more than 10%, comments, decisions, the send-time recheck, the Owners' emergency bypass, and scheduling or starting the send through the sending engine.
Package approvals implements send approvals (add-on 3.8, 5.12) and the Review & send flow around them (spec 7.5): the workspace policy and its rules, approval requests with a snapshot of what they cover (content and subject, audience definition, route, schedule), invalidation with the exact diff when any of it changes or the audience moves more than 10%, comments, decisions, the send-time recheck, the Owners' emergency bypass, and scheduling or starting the send through the sending engine.
apptest
Package apptest runs the whole HTTP stack against a fresh test database so API behaviour can be tested end to end: middleware, authz, handlers, SQL.
Package apptest runs the whole HTTP stack against a fresh test database so API behaviour can be tested end to end: middleware, authz, handlers, SQL.
audience
Package audience implements the Audience screens (spec 5.6, 7.9): contacts with saved views and bulk actions, contact profiles with consent history and an activity timeline, lists and custom fields, engagement tiers and the sunset policy, list health, audited CSV export and the shared suppression list.
Package audience implements the Audience screens (spec 5.6, 7.9): contacts with saved views and bulk actions, contact profiles with consent history and an activity timeline, lists and custom fields, engagement tiers and the sunset policy, list health, audited CSV export and the shared suppression list.
audit
Package audit writes the immutable audit log: who did what to which target, before and after, from where, and whether it was allowed.
Package audit writes the immutable audit log: who did what to which target, before and after, from where, and whether it was allowed.
auditlog
Package auditlog serves the audit log (A5 §3.10, §5.14): filtered event list, event detail with before/after values, streamed CSV/JSON exports, streaming to a webhook and retention.
Package auditlog serves the audit log (A5 §3.10, §5.14): filtered event list, event detail with before/after values, streamed CSV/JSON exports, streaming to a webhook and retention.
authn
Package authn implements sign-in primitives: argon2id password hashing, opaque session and API tokens (only SHA-256 hashes are stored), TOTP, recovery codes, the optional breached-password check, passkeys and OIDC.
Package authn implements sign-in primitives: argon2id password hashing, opaque session and API tokens (only SHA-256 hashes are stored), TOTP, recovery codes, the optional breached-password check, passkeys and OIDC.
authz
Package authz is ReputeCast's small, in-house authorization layer.
Package authz is ReputeCast's small, in-house authorization layer.
automations
Package automations implements visual flows (spec 7.10): the React Flow graph and its validation, versions with a diff and publish, the runs engine on River and per-step stats.
Package automations implements visual flows (spec 7.10): the React Flow graph and its validation, versions with a diff and publish, the runs engine on River and per-step stats.
campaigns
Package campaigns implements campaigns: the list and summary, drafts and the composer's storage, versions, scheduling and sending state.
Package campaigns implements campaigns: the list and summary, drafts and the composer's storage, versions, scheduling and sending state.
cli
Package cli implements the reputecast command line with cobra.
Package cli implements the reputecast command line with cobra.
config
Package config loads ReputeCast configuration from defaults, an optional YAML file, REPUTECAST_* environment variables and command-line flags, in that order of precedence (later wins).
Package config loads ReputeCast configuration from defaults, an optional YAML file, REPUTECAST_* environment variables and command-line flags, in that order of precedence (later wins).
connect
Package connect implements "Connect a sending provider" (spec 5.7, 7.2): the provider catalog built from the adapter registry, and a six-step setup (provider, connection, domain verification, test send, streams, contacts) whose progress is kept in provider_setups so a reload resumes the same step.
Package connect implements "Connect a sending provider" (spec 5.7, 7.2): the provider catalog built from the adapter registry, and a six-step setup (provider, connection, domain verification, test send, streams, contacts) whose progress is kept in provider_setups so a reload resumes the same step.
contentcheck
Package contentcheck finds deliverability problems in an email's content: size against Gmail's 102 KB clipping limit, images without alt text, the image-to-text ratio, links on URI blocklists, URL shorteners and broken links, a missing unsubscribe link or postal address, Liquid errors, spam heuristics in the subject, and the plain-text part.
Package contentcheck finds deliverability problems in an email's content: size against Gmail's 102 KB clipping limit, images without alt text, the image-to-text ratio, links on URI blocklists, URL shorteners and broken links, a missing unsubscribe link or postal address, Liquid errors, spam heuristics in the subject, and the plain-text part.
db
Package db opens the Postgres pool and runs schema migrations (goose for ReputeCast's own tables, rivermigrate for River's job tables).
Package db opens the Postgres pool and runs schema migrations (goose for ReputeCast's own tables, rivermigrate for River's job tables).
deliverability
Package deliverability builds the Deliverability screen (spec 7.8): health per sending domain and dedicated IP (shared pools are checked at domain level), provider account health against each provider's own thresholds, blocklists (via HostRepute when connected, else a built-in DNSBL set), Postmaster Tools, SNDS, DMARC reports and the incident timeline.
Package deliverability builds the Deliverability screen (spec 7.8): health per sending domain and dedicated IP (shared pools are checked at domain level), provider account health against each provider's own thresholds, blocklists (via HostRepute when connected, else a built-in DNSBL set), Postmaster Tools, SNDS, DMARC reports and the incident timeline.
demo
Package demo loads the sample data from the design ("Acme Newsletter") so the app can be explored, screenshotted and compared with the prototype.
Package demo loads the sample data from the design ("Acme Newsletter") so the app can be explored, screenshotted and compared with the prototype.
dnscheck
Package dnscheck answers the DNS questions deliverability depends on: SPF, DKIM, DMARC (with policy discovery), BIMI and MAIL FROM alignment for sending domains, forward-confirmed reverse DNS for IPs, and DNSBL listings for both.
Package dnscheck answers the DNS questions deliverability depends on: SPF, DKIM, DMARC (with policy discovery), BIMI and MAIL FROM alignment for sending domains, forward-confirmed reverse DNS for IPs, and DNSBL listings for both.
domains
Package domains implements sending domains and sender identities (spec 7.13 Settings › Senders, and the domain step of 7.2): the DNS records each sending provider needs (through the provider's domain API when it has one), live verification with internal/dnscheck, the authentication summary per domain, verification per sender and sending provider, the default sender of each stream, custom link-tracking domains, adding records through the Cloudflare API, and a periodic re-verification job.
Package domains implements sending domains and sender identities (spec 7.13 Settings › Senders, and the domain step of 7.2): the DNS records each sending provider needs (through the provider's domain API when it has one), live verification with internal/dnscheck, the authentication summary per domain, verification per sender and sending provider, the default sender of each stream, custom link-tracking domains, adding records through the Cloudflare API, and a periodic re-verification job.
emailaddr
Package emailaddr checks and classifies email addresses for the audience and the importer: syntax, role addresses, disposable domains, likely typos, spam-trap-like patterns, mailbox providers and masking.
Package emailaddr checks and classifies email addresses for the audience and the importer: syntax, role addresses, disposable domains, likely typos, spam-trap-like patterns, mailbox providers and masking.
forms
Package forms implements signup forms and the settings of the public pages (spec 5.12, 7.12): embedded, popup and hosted forms, the embed script, spam protection, the submission pipeline the public pages call, double opt-in emails on the System stream, and the pages' branding, custom domain and Turnstile keys.
Package forms implements signup forms and the settings of the public pages (spec 5.12, 7.12): embedded, popup and hosted forms, the embed script, spam protection, the submission pipeline the public pages call, double opt-in emails on the System stream, and the pages' branding, custom domain and Turnstile keys.
hostrepute
Package hostrepute connects a workspace to HostRepute (hostrepute.com), the sibling email-reputation service: OAuth 2 (PKCE) or API-key connection, encrypted tokens, a River job that syncs blocklist, Postmaster, SNDS, DMARC and alert data, "Add to monitoring" and disconnect.
Package hostrepute connects a workspace to HostRepute (hostrepute.com), the sibling email-reputation service: OAuth 2 (PKCE) or API-key connection, encrypted tokens, a River job that syncs blocklist, Postmaster, SNDS, DMARC and alert data, "Add to monitoring" and disconnect.
hostrepute/hrtest
Package hrtest is a fake HostRepute (API and OAuth server) for tests.
Package hrtest is a fake HostRepute (API and OAuth server) for tests.
imports
Package imports is the migration importer (spec 5.8, 7.11): CSV and XLSX uploads and API importers for Brevo, Mailchimp, MailerLite, listmonk and Keila.
Package imports is the migration importer (spec 5.8, 7.11): CSV and XLSX uploads and API importers for Brevo, Mailchimp, MailerLite, listmonk and Keila.
ingest
Package ingest receives provider events: the webhook endpoint (POST /hooks/{adapter}/{token}) verifies the signature, stores the raw payload and answers immediately; a River job normalizes it later.
Package ingest receives provider events: the webhook endpoint (POST /hooks/{adapter}/{token}) verifies the signature, stores the raw payload and answers immediately; a River job normalizes it later.
instance
Package instance is the Instance admin area (add-on spec 3.3, 3.13, 5.10): accounts across workspaces, workspaces (with a 7-day restore hold), the authentication policy, instance settings and version & updates.
Package instance is the Instance admin area (add-on spec 3.3, 3.13, 5.10): accounts across workspaces, workspaces (with a 7-day restore hold), the authentication policy, instance settings and version & updates.
jobs
Package jobs wires River, the Postgres-backed job queue.
Package jobs wires River, the Postgres-backed job queue.
linktoken
Package linktoken signs the tokens embedded in emails: open pixel, click redirect, one-click unsubscribe (RFC 8058), preference center, view online and double opt-in confirmation links.
Package linktoken signs the tokens embedded in emails: open pixel, click redirect, one-click unsubscribe (RFC 8058), preference center, view online and double opt-in confirmation links.
liquid
Package liquid renders personalization in subjects, preheaders and email bodies with Liquid (osteele/liquid): {{ first_name | default: "there" }}.
Package liquid renders personalization in subjects, preheaders and email bodies with Liquid (osteele/liquid): {{ first_name | default: "there" }}.
logging
Package logging configures log/slog for the process.
Package logging configures log/slog for the process.
mailer
Package mailer sends ReputeCast's own system mail (password resets, team invites, double opt-in, approval notifications) through whichever sending provider is routed to the System stream.
Package mailer sends ReputeCast's own system mail (password resets, team invites, double opt-in, approval notifications) through whichever sending provider is routed to the System stream.
maintenance
Package maintenance runs housekeeping jobs: expired sessions and sign-in challenges, audit-log retention, and lists deleted longer ago than they can be restored.
Package maintenance runs housekeeping jobs: expired sessions and sign-in challenges, audit-log retention, and lists deleted longer ago than they can be restored.
mcpserver
Package mcpserver is ReputeCast's Model Context Protocol server (main spec 5.13, A5 §5.13).
Package mcpserver is ReputeCast's Model Context Protocol server (main spec 5.13, A5 §5.13).
media
Package media is the workspace image library used by the composer's asset manager.
Package media is the workspace image library used by the composer's asset manager.
meta
Package meta serves instance information the web app needs before sign-in: the instance name and logo, which sign-in methods are enabled and the version.
Package meta serves instance information the web app needs before sign-in: the instance name and logo, which sign-in methods are enabled and the version.
mjml
Package mjml works with MJML documents on the server: a tolerant parser for outlines, warnings and wireframes, the server-side compiler (gomjml, MJML 4.15) used when content arrives as MJML only (API and automation sends), and head helpers that keep <mj-title>/<mj-preview> in step with the subject and preheader.
Package mjml works with MJML documents on the server: a tolerant parser for outlines, warnings and wireframes, the server-side compiler (gomjml, MJML 4.15) used when content arrives as MJML only (API and automation sends), and head helpers that keep <mj-title>/<mj-preview> in step with the subject and preheader.
netguard
Package netguard makes outbound HTTP requests to user-supplied URLs (outgoing webhooks, the audit stream) safe from server-side request forgery: the address is checked after DNS resolution, at connect time, so a hostname can't point at loopback, private, link-local or metadata addresses, and redirects are never followed.
Package netguard makes outbound HTTP requests to user-supplied URLs (outgoing webhooks, the audit stream) safe from server-side request forgery: the address is checked after DNS resolution, at connect time, so a hostname can't point at loopback, private, link-local or metadata addresses, and redirects are never followed.
notify
Package notify creates in-app notifications (A5 §3.12) and fans them out to the members who should see them.
Package notify creates in-app notifications (A5 §3.12) and fans them out to the members who should see them.
overview
Package overview builds the workspace Overview (spec 7.1): sender health, the next scheduled campaign, provider cards, subscriber growth and tiers, and recent campaigns.
Package overview builds the workspace Overview (spec 7.1): sender health, the next scheduled campaign, provider cards, subscriber growth and tiers, and recent campaigns.
passwordreuse
Package passwordreuse enforces the re-use rule of the instance password policy (Instance admin › Authentication › Password policy): a new password can't be any of the person's last N passwords, the current one included.
Package passwordreuse enforces the re-use rule of the instance password policy (Instance admin › Authentication › Password policy): a new password can't be any of the person's last N passwords, the current one included.
permcheck
Package permcheck checks a second permission inside a handler, for operations whose requirement depends on the request (saving a segment in SQL mode needs segments:sql on top of segments:edit).
Package permcheck checks a second permission inside a handler, for operations whose requirement depends on the request (saving a segment in SQL mode needs segments:sql on top of segments:edit).
providers
Package providers defines the pluggable sending-provider contract.
Package providers defines the pluggable sending-provider contract.
providers/apiclient
Package apiclient is the small JSON-over-HTTP client the API adapters (Postmark, Postal…) share: timeouts, a response size limit, and mapping of HTTP failures to providers.CallError so health checks and the sending pipeline can tell an outage from throttling from rejected credentials.
Package apiclient is the small JSON-over-HTTP client the API adapters (Postmark, Postal…) share: timeouts, a response size limit, and mapping of HTTP failures to providers.CallError so health checks and the sending pipeline can tell an outage from throttling from rejected credentials.
providers/azureacs
Package azureacs is the Azure Communication Services Email adapter, on the data-plane REST API without the Azure SDK.
Package azureacs is the Azure Communication Services Email adapter, on the data-plane REST API without the Azure SDK.
providers/bounce
Package bounce maps SMTP replies and enhanced status codes (RFC 3463) to ReputeCast's shared bounce taxonomy, so every adapter classifies the same diagnostic the same way: mailbox_unknown, mailbox_full, domain_invalid, policy_block, spam_block, reputation, temporary, other.
Package bounce maps SMTP replies and enhanced status codes (RFC 3463) to ReputeCast's shared bounce taxonomy, so every adapter classifies the same diagnostic the same way: mailbox_unknown, mailbox_full, domain_invalid, policy_block, spam_block, reputation, temporary, other.
providers/brevo
Package brevo is the Brevo (formerly Sendinblue) adapter, through the transactional email API v3.
Package brevo is the Brevo (formerly Sendinblue) adapter, through the transactional email API v3.
providers/contracttest
Package contracttest is the shared test suite every sending-provider adapter must pass (TECH_STACK note 10): registration and capabilities, Send (success, permanent rejection, outage, rejected credentials) against a fake of the provider's API, and ParseWebhook (signature verification and normalization) against recorded payloads.
Package contracttest is the shared test suite every sending-provider adapter must pass (TECH_STACK note 10): registration and capabilities, Send (success, permanent rejection, outage, rejected credentials) against a fake of the provider's API, and ParseWebhook (signature verification and normalization) against recorded payloads.
providers/flex
Package flex holds setting types that accept what a connection form may store.
Package flex holds setting types that accept what a connection form may store.
providers/httpgeneric
Package httpgeneric is the generic HTTP adapter (spec 5.2).
Package httpgeneric is the generic HTTP adapter (spec 5.2).
providers/mailgun
Package mailgun is the Mailgun adapter (US and EU regions).
Package mailgun is the Mailgun adapter (US and EU regions).
providers/mailjet
Package mailjet is the Mailjet adapter (Send API v3.1).
Package mailjet is the Mailjet adapter (Send API v3.1).
providers/manage
Package manage is the sending-providers domain: the provider list with health, quota, cost and capabilities (spec 7.3), the health job (outages, rejected credentials, webhooks silent, recovery, failover per stream), provider actions (re-check, credentials, settings, tracking, webhooks, backfill, held broadcasts) and the Adapters tab.
Package manage is the sending-providers domain: the provider list with health, quota, cost and capabilities (spec 7.3), the health job (outages, rejected credentials, webhooks silent, recovery, failover per stream), provider actions (re-check, credentials, settings, tracking, webhooks, backfill, held broadcasts) and the Adapters tab.
providers/mimemsg
Package mimemsg renders a providers.Message as an RFC 5322 message with wneessen/go-mail, so the adapters that send raw MIME (Amazon SES, Postal, SMTP) produce byte-for-byte the same structure: multipart/alternative (text, then HTML), a Message-ID derived from the ReputeCast message id, and every header the sending pipeline set (List-Unsubscribe, Feedback-ID…).
Package mimemsg renders a providers.Message as an RFC 5322 message with wneessen/go-mail, so the adapters that send raw MIME (Amazon SES, Postal, SMTP) produce byte-for-byte the same structure: multipart/alternative (text, then HTML), a Message-ID derived from the ReputeCast message id, and every header the sending pipeline set (List-Unsubscribe, Feedback-ID…).
providers/postal
Package postal is the adapter for a self-hosted Postal server (postalserver.io).
Package postal is the adapter for a self-hosted Postal server (postalserver.io).
providers/postmark
Package postmark is the Postmark adapter.
Package postmark is the Postmark adapter.
providers/remote
Package remote runs community adapters: sending adapters that live in their own process and speak the adapter protocol (docs/adapters.md, "Community adapters"), signed JSON over HTTP(S).
Package remote runs community adapters: sending adapters that live in their own process and speak the adapter protocol (docs/adapters.md, "Community adapters"), signed JSON over HTTP(S).
providers/remote/remotetest
Package remotetest is a fake community adapter process for tests: a small reference implementation of the adapter side of the protocol (docs/adapters.md) in Go.
Package remotetest is a fake community adapter process for tests: a small reference implementation of the adapter side of the protocol (docs/adapters.md) in Go.
providers/resend
Package resend is the Resend adapter (resend.com).
Package resend is the Resend adapter (resend.com).
providers/sendgrid
Package sendgrid is the Twilio SendGrid adapter (v3 API).
Package sendgrid is the Twilio SendGrid adapter (v3 API).
providers/ses
Package ses is the Amazon SES adapter (SES API v2 through aws-sdk-go-v2), with events delivered through SNS.
Package ses is the Amazon SES adapter (SES API v2 through aws-sdk-go-v2), with events delivered through SNS.
providers/simulator
Package simulator is the demo transport: a sending provider that touches no network.
Package simulator is the demo transport: a sending provider that touches no network.
providers/smtp
Package smtp is the generic SMTP adapter (wneessen/go-mail).
Package smtp is the generic SMTP adapter (wneessen/go-mail).
providers/smtp/bouncebox
Package bouncebox reads the bounce mailbox of an SMTP provider over IMAP (github.com/emersion/go-imap/v2, isolated here because it is still in beta) or POP3 (a small client in this package).
Package bouncebox reads the bounce mailbox of an SMTP provider over IMAP (github.com/emersion/go-imap/v2, isolated here because it is still in beta) or POP3 (a small client in this package).
providers/smtp/dsn
Package dsn parses bounce and complaint reports that arrive by email: delivery status notifications (RFC 3464, multipart/report; report-type=delivery-status) and abuse reports (ARF, RFC 5965, report-type=feedback-report).
Package dsn parses bounce and complaint reports that arrive by email: delivery status notifications (RFC 3464, multipart/report; report-type=delivery-status) and abuse reports (ARF, RFC 5965, report-type=feedback-report).
providers/sparkpost
Package sparkpost is the SparkPost adapter (US and EU).
Package sparkpost is the SparkPost adapter (US and EU).
providers/state
Package state describes what ReputeCast stores about a connected provider in the providers table's JSON columns (capability snapshot, health, pricing, limits, provider-side tracking) and the display helpers every screen shares (short names, chart colours).
Package state describes what ReputeCast stores about a connected provider in the providers table's JSON columns (capability snapshot, health, pricing, limits, provider-side tracking) and the display helpers every screen shares (short names, chart colours).
providers/webhookauth
Package webhookauth holds the webhook authentication schemes several sending providers share, so each adapter verifies them the same way: Standard Webhooks (the Svix scheme Resend uses), HMAC signatures over the body, and shared secrets sent as basic auth or in a header.
Package webhookauth holds the webhook authentication schemes several sending providers share, so each adapter verifies them the same way: Standard Webhooks (the Svix scheme Resend uses), HMAC signatures over the body, and shared secrets sent as basic auth or in a header.
publicpages
Package publicpages serves the pages subscribers see (spec 5.12, 7.12), server-rendered with html/template under the layout of internal/publicurl:
Package publicpages serves the pages subscribers see (spec 5.12, 7.12), server-rendered with html/template under the layout of internal/publicurl:
publicurl
Package publicurl builds the absolute URLs that appear in emails and on public pages, so the code that writes them (sending, tracking, forms, reports) and the handlers that serve them agree on one layout:
Package publicurl builds the absolute URLs that appear in emails and on public pages, so the code that writes them (sending, tracking, forms, reports) and the handlers that serve them agree on one layout:
readiness
Package readiness is Send Readiness (spec 5.1, 7.5): every check a campaign must pass before it goes out, each Pass, Warn, Block or Unknown with its evidence and a fix, plus the estimates around the send (final audience, route, cost and duration, throttling per mailbox provider).
Package readiness is Send Readiness (spec 5.1, 7.5): every check a campaign must pass before it goes out, each Pass, Warn, Block or Unknown with its evidence and a fix, plus the estimates around the send (final audience, route, cost and duration, throttling per mailbox provider).
reports
Package reports builds the campaign report (spec 7.7, honest analytics 5.5) from campaign_counters, its exports and read-only report links, whose public page shows the same aggregate numbers and nothing else.
Package reports builds the campaign report (spec 7.7, honest analytics 5.5) from campaign_counters, its exports and read-only report links, whose public page shows the same aggregate numbers and nothing else.
roles
Package roles implements Roles & permissions (A5 §3.6, §5.9): the four read-only built-in roles, custom roles and the impact preview shown before saving.
Package roles implements Roles & permissions (A5 §3.6, §5.9): the four read-only built-in roles, custom roles and the impact preview shown before saving.
routing
Package routing decides which sending provider delivers each email: rules per stream (Broadcasts, Automations, System) with conditions on the list, the sender domain and the recipient's mailbox provider, a deterministic weighted split for migrations and warm-up, a fallback per stream and the failover policy.
Package routing decides which sending provider delivers each email: rules per stream (Broadcasts, Automations, System) with conditions on the list, the sender domain and the recipient's mailbox provider, a deterministic weighted split for migrations and warm-up, a fallback per stream and the failover policy.
secrets
Package secrets encrypts provider credentials, OIDC client secrets, TOTP seeds and other write-only values at rest with AES-256-GCM.
Package secrets encrypts provider credentials, OIDC client secrets, TOTP seeds and other write-only values at rest with AES-256-GCM.
segments
Package segments implements audience segments (spec 5.10, 7.9): a condition builder with AND/OR groups compiled to parameterized SQL, a live count with the tier mix, the generated SQL shown to power users, and SQL mode (segments:sql) where people write read-only SQL over the segment views.
Package segments implements audience segments (spec 5.10, 7.9): a condition builder with AND/OR groups compiled to parameterized SQL, a live count with the tier mix, the generated SQL shown to power users, and SQL mode (segments:sql) where people write read-only SQL over the segment views.
sending
Package sending runs campaign sends: it builds the recipient list, applies suppressions, routes each recipient to a sending provider, throttles per provider and per mailbox provider, sends in batches through River jobs, updates live counters and pauses automatically when thresholds trip.
Package sending runs campaign sends: it builds the recipient list, applies suppressions, routes each recipient to a sending provider, throttles per provider and per mailbox provider, sends in batches through River jobs, updates live counters and pauses automatically when thresholds trip.
sending/engine
Package engine is ReputeCast's sending engine (spec 5.3, 7.6): it builds a campaign's recipient list, routes, renders and hands every message to its sending provider within rate limits and throttles, watches bounce, complaint and outage signals and pauses what they concern, sends automation emails, and serves the live monitor's snapshot and stream.
Package engine is ReputeCast's sending engine (spec 5.3, 7.6): it builds a campaign's recipient list, routes, renders and hands every message to its sending provider within rate limits and throttles, watches bounce, complaint and outage signals and pauses what they concern, sends automation emails, and serves the live monitor's snapshot and stream.
server
Package server builds the HTTP stack: middleware, security headers, the embedded single-page app and graceful shutdown.
Package server builds the HTTP stack: middleware, security headers, the embedded single-page app and graceful shutdown.
sessionext
Package sessionext tells the web app when the current browser session will end and lets the person extend it, so the app can warn before an idle timeout instead of losing unsaved work.
Package sessionext tells the web app when the current browser session will end and lets the person extend it, so the app can warn before an idle timeout instead of losing unsaved work.
sso
Package sso implements single sign-on over OpenID Connect (add-on spec 3.2, 5.11) and social sign-in with Google, Microsoft and GitHub (3.1): provider setup, claim and group mappings, just-in-time accounts, domain enforcement with break-glass Owners, a dry-run test sign-in and the browser flows (state, nonce and PKCE).
Package sso implements single sign-on over OpenID Connect (add-on spec 3.2, 5.11) and social sign-in with Google, Microsoft and GitHub (3.1): provider setup, claim and group mappings, just-in-time accounts, domain enforcement with break-glass Owners, a dry-run test sign-in and the browser flows (state, nonce and PKCE).
sso/ssotest
Package ssotest is a fake OpenID Connect issuer (and a fake GitHub) for tests and local screenshots: discovery, signing keys, an authorization endpoint that approves at once, a token endpoint that checks the client secret and the PKCE verifier and returns a signed ID token with the nonce, and userinfo.
Package ssotest is a fake OpenID Connect issuer (and a fake GitHub) for tests and local screenshots: discovery, signing keys, an authorization endpoint that approves at once, a token endpoint that checks the client secret and the PKCE verifier and returns a signed ID token with the nonce, and userinfo.
sso/ssotest/fakeidp command
Command fakeidp runs the test OpenID Connect issuer locally, so the SSO setup screens can be tried end to end without a real identity provider:
Command fakeidp runs the test OpenID Connect issuer locally, so the SSO setup screens can be tried end to end without a real identity provider:
suppressions
Package suppressions keeps the shared suppression list in sync with each sending provider: addresses suppressed at a provider are pulled into the shared list (a bounce at one provider stops mail everywhere) and the shared list is pushed to providers with a suppression API.
Package suppressions keeps the shared suppression list in sync with each sending provider: addresses suppressed at a provider are pulled into the shared list (a bounce at one provider stops mail everywhere) and the shared list is pushed to providers with a suppression API.
systemmail
Package systemmail sends ReputeCast's own mail (password resets, email changes, team invitations, notifications, double opt-in confirmations, test messages) through the workspace's System-stream route, whose fallback takes over when the provider is down or refuses the message.
Package systemmail sends ReputeCast's own mail (password resets, email changes, team invitations, notifications, double opt-in confirmations, test messages) through the workspace's System-stream route, whose fallback takes over when the provider is down or refuses the message.
team
Package team manages the people of a workspace (A5 §3.5, §5.8): members, invitations, role and scope changes, deactivation and removal.
Package team manages the people of a workspace (A5 §3.5, §5.8): members, invitations, role and scope changes, deactivation and removal.
templates
Package templates holds the composer's template gallery: the starter templates that ship with ReputeCast (MJML files embedded in the binary, their placeholder images served at /media/starters/), the workspace's saved templates and its saved sections (reusable blocks).
Package templates holds the composer's template gallery: the starter templates that ship with ReputeCast (MJML files embedded in the binary, their placeholder images served at /media/starters/), the workspace's saved templates and its saved sections (reusable blocks).
testdb
Package testdb gives integration tests a fresh, migrated Postgres database.
Package testdb gives integration tests a fresh, migrated Postgres database.
tracking
Package tracking serves the open pixel and the click redirect that go in every tracked email, and records opens and clicks honestly: human opens separated from machine opens (Apple Mail Privacy Protection, image proxy prefetches, security scanners) and bot clicks kept out of the counts.
Package tracking serves the open pixel and the click redirect that go in every tracked email, and records opens and clicks honestly: human opens separated from machine opens (Apple Mail Privacy Protection, image proxy prefetches, security scanners) and bot clicks kept out of the counts.
version
Package version exposes build information set by the linker.
Package version exposes build information set by the linker.
warmup
Package warmup plans and runs the warm-up of a new sending provider or dedicated IP: a daily volume ramp, the most engaged contacts first, an automatic slowdown when bounces or complaints rise, and a Broadcast share that grows with the plan (10% → 15% → 25% → 40%).
Package warmup plans and runs the warm-up of a new sending provider or dedicated IP: a daily volume ramp, the most engaged contacts first, an automatic slowdown when bounces or complaints rise, and a Broadcast share that grows with the plan (10% → 15% → 25% → 40%).
webhooks
Package webhooks delivers normalized ReputeCast events to the endpoints a workspace registers (main spec 7.13).
Package webhooks delivers normalized ReputeCast events to the endpoints a workspace registers (main spec 7.13).
workspaces
Package workspaces creates and manages workspaces: built-in roles, the owner membership, settings, transfer of ownership and deletion.
Package workspaces creates and manages workspaces: built-in roles, the owner membership, settings, transfer of ownership and deletion.
Package migrations embeds the goose SQL migrations so the single binary can migrate its own database (`reputecast migrate up`).
Package migrations embeds the goose SQL migrations so the single binary can migrate its own database (`reputecast migrate up`).
sdk
client-go module
Package web embeds the built single-page app (web/dist) into the binary.
Package web embeds the built single-page app (web/dist) into the binary.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL