Claros v0.6.3

v0.6.3 - mobile web compatibility

Claros v0.6.2

v0.6.2 - lighter bg for light mode.

No functional changes.

Claros v0.6.1

v0.6.1 - documentation and screenshots

No functional changes. The README and guide now show the product with real
history in it rather than an empty install, including the lifecycle retention
grid.

• Retaken screenshots across the README and guide, from one consistent install
• Added the lifecycle retention view
• A repeatable demo seeder for local development

Claros v0.6.0

v0.6.0 - first public release

Claros is an AI-native lifecycle email platform you can run yourself. Events come
in, contacts move through a lifecycle, flows decide what to send, and a human
approves before anything reaches an inbox.

Installing

• Three commands: prepare, start, open the browser
• The installer generates your secrets, tests the database and applies migrations
• First account is claimed in the browser. No default credentials, no passwords
• Bundled Postgres by default, or point at your own with --database-url

Without an LLM key

• Ready-made flows with human-written copy that work out of the box
• Write your own flows and email copy on any supported trigger
• The AI is an upgrade, not a prerequisite

With one

• Describe a campaign in plain language and let it compile into a plan you review
• The AI drafts each email for each contact, and you approve before it sends

Sending

• SMTP or Resend, verified when you save the credentials
• A branded shell around every email, with unsubscribe and postal address built in
• Sent mail log, delivery timeline, suppression list
• Sending pace controls: per-contact limits, send windows, batch size

Getting events in

• Segment-compatible API, so existing SDKs work by changing the endpoint
• A browser snippet, a batch endpoint, and server-side sending from any language

Documentation

• Quickstart, installation, deployment, concepts, FAQ, ingestion, and a library of
  flow prompts to start from

Known limits

• SMTP reports no delivery events, so engagement tracking needs a provider with
  webhooks
• Volume ramping is not implemented
• Segment and manual trigger coverage is partial
• Schema still changes between releases, which is why this is 0.x

Claros v0.5.2

v0.5.2 - the first version a self-hoster can actually use

Claros v0.5.1

v0.5.1 - the first version a self-hoster can actually use

Claros v0.4.1

v0.4.1 - Operational visibility

This release adds the ability to see what the running container actually has,
rather than what the repository says it should have.

Added

• GET /version (public, no database access): commit SHA, edition, build time.
  The SHA is injected at image build time.
• GET /v1/diagnostics (authenticated): for each encryption key, whether it is
  present, its byte length, and a fingerprint. Key values are never returned.
• claros doctor: compares local HEAD against the deployed commit, reports the
  database target and migration state, transport config counts and webhook
  secret fingerprint, and whether the local and container keys agree.
  Read only, it changes nothing.
• The deploy pipeline now polls /version after deploying and fails the job if
  the deployed commit does not match the pushed commit. A missing secret no
  longer produces a green job with skipped deploy steps.

Why this exists
A webhook and unsubscribe outage took a day to diagnose. The signature
verification code was correct throughout. The container was running a stale
encryption key because a secret had been rotated without restarting the
container, so stored transport configs could not be decrypted. Nothing in the
system could show that. Rotating a secret has no effect until the container
restarts, and a green deploy can keep serving the previous image for several
minutes.

Not working or not included

• Dashboard: there is no UI. Phase 5 has only just started.
• Cloud edition: brain-cloud is a stub and the container refuses to start with
  CLAROS_EDITION=cloud. Self-host community edition is the only working mode.
• Unsubscribe: the link resolves and the page renders, but suppression on click
  and skipping of that address on later sends are not verified end to end.
• Transports: Resend only. SES and SMTP adapters are not implemented.
• No per-tenant circuit breaker and no daily send cap.
• Knowledge base auto-crawl is not implemented.
• There is no written end to end smoke test yet.

Known sharp edge
transport set replaces the config instead of merging it. If webhook_secret is
omitted it is silently dropped, and every subsequent webhook returns 400 with
no logged reason.

Claros v0.4.0

v0.4.0 - Sending

Claros now sends email.

What works in this release:

• Approved messages are delivered through Resend. Every lifecycle email
  carries RFC 8058 one-click unsubscribe headers and a CAN-SPAM footer
  with the sender's postal address. A tenant without a postal address
  configured does not send at all rather than sending a non-compliant
  message.
• Unsubscribing works. The one-click endpoint and the hosted page both
  write to the suppression list, and the suppression gate is checked
  before every send.
• Bounces, complaints, opens, and clicks are ingested from signed
  provider webhooks. Permanent bounces and complaints suppress the
  address automatically.
• Messages wait for human approval by default. Flows can be set to
  approve automatically.
• An operator CLI covers first-run setup: postal address, model
  provider, and transport credentials, all stored encrypted. Credentials
  never live in environment files.
• Login links are emailed once transport is configured, and printed to
  the console before that, so a fresh install is usable immediately.

What does not work yet:

• Resend is the only transport. SES and SMTP are not implemented; the
  CLI accepts those names but nothing will send.
• Bounce and open tracking needs a publicly reachable install and a
  webhook registered with the provider. It is untested against live
  provider traffic.
• There is no dashboard. Everything is API or CLI.
• No automatic pause on high bounce rates, and the per-tenant daily
  limit is stored but not enforced.
• The knowledge base has no file upload, no crawling, and no search
  endpoint. Entries are created through the API.

Not ready for production use.

Claros v0.3.1

v0.3.1 - The Brain

Claros can now decide, write, and hold an email for review.

What works in this release:

• Flows described in natural language compile once into a deterministic
  plan. The engine runs the plan; the model is not in the timing loop.
• For each scheduled message the engine decides whether contact is
  warranted, drafts the email, and assesses its own draft before the
  message is queued for human approval. Drafts judged not worth sending
  are recorded rather than discarded silently.
• A knowledge base with vector search. Entries are embedded in the
  background and the most relevant ones are retrieved for each draft.
• Suppression list import.
• Three business model templates that seed lifecycle thresholds,
  throttle settings, and a starting set of flows.
• Self-hosted installs work fully with your own model provider key.

What does not work yet:

• Nothing is sent. There is no email transport in this release, and no
  unsubscribe handling. Both arrive next.
• There is no dashboard. Everything is API only.
• The knowledge base has no automatic crawling. Entries are created
  through the API.
• Vector search quality is untuned. Retrieval thresholds are starting
  values, not calibrated against real data.

Not ready for production use.

Claros v0.2.2

v0.2.2 — Engine Core

The lifecycle engine now runs end to end.

• Segment-compatible event ingestion (track and identify) with API key auth,
  server-side deduplication, and partitioned event storage
• Contact model with trait merging, conflict recording, and a unified lifecycle
  state machine covering seven states
• Flows defined in plain language and compiled once by an LLM into a
  deterministic execution plan, with a bring-your-own key
• Flow execution: enrollment with priority and re-entry rules, step advancement,
  exit conditions, and engagement depth from incremental counters
• Throttle gate with suppression, frequency caps, and timezone-aware send windows
• Drain and reap workers with crash recovery

Not yet functional: email content generation and actual sending. Messages are
created, throttled, and queued, but no transport exists yet, so nothing leaves
the system.