Product overview | User manual

AutoBlocks (AutoBlocks.ai) is a multi-tenant self-serve SaaS that helps ambitious individuals automate routine personal tasks. You build AutoBlocks — guided automation units — instead of wiring a blank canvas. Marketing lives on autoblocks.pro; the running product lives on autoblocks.run.

AutoBlocks is not a general-purpose scripting platform, integration marketplace, or team collaboration suite in Phase 1. It is calm, template-first automation with bounded AI assist and visible value quickly.

Core product pillars

Pillar	What it means for you
Visible value first	Templates and onboarding get you to a working AutoBlock in minutes
Trust over magic	Every step is reviewable; AI suggests, you accept or reject
Guided by default	Wizard-led creation; no unrestricted user code
Mobile useful	Summary editing and dashboard on phone; richer schedule controls on desktop
Structured flexibility	Triggers, steps, and rules within Phase 1 constructs
AI assists, you control	Draft, refine, repair, explain — never silent auto-changes

Who AutoBlocks is for

Persona	Typical use
Ambitious individual	Daily reminders, inbox nudges, personal check-ins
Solo operator	Webhook relays, payment alerts, lead capture forwarding
Small team (light)	Standup pings, status checks — not full team RBAC

Phase 1 optimizes for individuals first, then solo operators, then small teams with simple shared patterns.

Logged out vs logged in

State	Where	What you can do
Logged out	autoblocks.pro	Home, pricing, docs, changelog, legal, help chat
Logged out	autoblocks.run/signup	Create account, start free trial
Logged in	autoblocks.run	Dashboard, wizard, templates, activity, billing, settings

Compare plans on .pro; manage subscription and usage on .run/billing.

Phase 1 — included

Capability	User-facing term	Notes
Manual trigger	Run on demand	From dashboard or routine detail
Scheduled trigger	Recurring time	Cron on desktop; simple schedules on mobile
Inbound webhook trigger	External POST starts a run	Personal endpoint per AutoBlock
Notifications	Email + in-app	Resend in production; preferences in Settings
Outbound webhooks	Step action	POST payload to your URL — not a trigger
Storage / logging	Step action	Persist run output for Activity review
Template library	`/templates`	9+ catalog entries in `packages/template-catalog`
Wizard-led creation	`/routines/new`	Template or AI-guided alternate path
Bounded AI assist	In-product only	Auth required; tenant-scoped API
Billing	Starter + Plus	14-day trial; monthly or annual
Activity history	`/activity`	Every run with status and plain-language failures

Phase 1 — explicitly excluded

Not available	Why
Custom user scripting	Trust and tenant safety
Unrestricted code generation	AI maps only to supported constructs
Broad integration marketplace	Phase 1 is template + webhook patterns
White-label architecture	Consumer brand focus
Advanced team collaboration	Deferred past Phase 1
Persistent chat-first product mode	AI assists setup, not daily chat ops
Book a call / sales scheduling	Removed — `/book` redirects to `/docs`

Plans at a glance

Plan	Monthly (USD)	Annual/mo (USD)	AutoBlocks	Executions/mo	Webhooks	Schedules
Trial (14 days)	Free	—	3	100	1	2
Starter	$12	$10	5	500	2	3
Plus	$24	$20	25	5,000	10	15

Full billing detail: Billing and plans. Source: packages/billing/src/plans.ts.

Design principles (consumer)

Visible value first — pick a template, activate, see Activity.
Trust over magic — review AI output before save.
Guided by default — wizard validates as you go.
Mobile useful, not compromised — bottom nav, card editing.
Structured flexibility — triggers + steps + optional rules.
AI assists, users stay in control — reject anything you do not trust.

System snapshot

flowchart LR
  User["You"]
  Pro["autoblocks.pro"]
  Run["autoblocks.run"]
  API["api.autoblocks.run"]

  User --> Pro
  User --> Run
  Pro -->|"CTA: Start trial"| Run
  Run --> API