Use cases

What people actually use Stratam for.

Four operator types, four sets of workflows. Concrete examples with the actual prompts and setup commands. Every workflow uses live tools — no mockups.

For founders

The 10 hours/week you stop spending on email + ops.

Inbox triage · calendar mgmt · customer follow-up · investor updates

You don't get paid to read email. Stratam reads your inbox in the morning, drafts the replies that only need approval, and archives the noise. Same for your calendar, your customer list, and the weekly investor update.

Morning inbox triage

Stratam reads every unread email, ranks by urgency, drafts replies in your voice for routine ones, flags the 2-3 that need personal attention.

summarize today's inbox + draft replies for the routine ones
→ google_email_search · 18 unread · 2.1sYou have 18 unread (12 routine, 4 follow-ups, 2 worth your attention). Worth your attention (drafted, not sent): 1. Sarah at Acme — wants to expand to 3 seats. I drafted a yes + 10% expansion discount. 2. Reuters reporter — asking about your last fundraise. I drafted a polite decline. Routine (drafted, sitting in Drafts): 3-12: SaaS renewal reminders + meeting confirmations. Trash candidates (15): 13-27: marketing, newsletters, recruiter spam. Want me to send the routine ones, archive the trash, and you'll review the two flagged?
Setup (one time)
Connect Gmail OAuth from /app/settings. Tell Stratam in Discord: read my inbox every weekday at 8am ET.

Calendar intelligence

Schedule meetings without the 6-email ping-pong. Stratam checks your real availability, proposes 3 slots, drafts the confirmation, and creates the event when accepted.

find 30 min for me + Casey + Dan next week, prefer afternoons
→ google_calendar_upcoming · 2.3sI checked everyone's availability. Three options for next week: Tuesday 5/26 · 2:00-2:30pm ET Wednesday 5/27 · 3:30-4:00pm ET Thursday 5/28 · 2:00-2:30pm ET I'll draft a calendar invite from your account once you pick. Reply with the day.
Setup
Same Gmail OAuth scope. Add JARVIS_USER_TZ=America/New_York so "afternoons" matches your local clock.

Weekly investor update (auto-draft)

Friday afternoon, Stratam pulls your Stripe MRR, GitHub commit activity, and key Discord conversations, drafts the update, and DMs you to review before sending.

→ stripe_summary + github_activity + memory_search · 8.4s📊 Weekly investor update, draft below. Week of May 12-18: • MRR: $12,430 (+$1,820 from new customers, +$340 expansion) • Churn: 1 logo ($89/mo), salvageable per support ticket • Customer count: 87 (+9 net) • Ship velocity: 23 commits, 4 BUILD_NOTES entries • Top intel: 3 prospects from X demo traffic — Casey at Forward, Dan at Pendulum, Maya at Bolt Lowlights: pricing experiment B2 down-pressured by Sample Y; reverting Tuesday. Approve and I'll send to the @founders + @board lists.
Setup
Configure Stripe + GitHub webhooks at /app/integrations. Schedule the cron: every Friday at 4pm ET, draft the weekly update.
For operators

Research and monitoring that runs while you sleep.

Competitor scrape · price monitoring · daily intel briefs · data pipelines

Operators don't need another chat window. They need a junior analyst who works 24/7. Stratam scrapes competitors on a schedule, watches prices, builds the CSV, runs the analysis, and surfaces the change worth your attention.

Competitor pricing scrape (multi-source)

Tell Stratam which competitors to track. He scrapes their pricing pages weekly via Playwright, builds a comparison CSV, and pings you when anyone changes their plans.

scrape pricing from linear.app, notion.so, asana.com — track weekly
→ browser_action × 3 · code_exec (pandas) · 14.2sScraped all 3. Built CSV at /root/.jarvis/intel/saas_pricing.csv. Linear: Free / Basic $8 / Standard $14 / Plus $20 Notion: Free / Plus $10 / Business $18 / Enterprise (call) Asana: Free / Starter $13.49 / Advanced $30.49 Median paid entry: $11/user/mo. Cheapest paid: Linear $8. Set up weekly cron (Monday 6am). I'll DM if any plan price changes more than 5%.
Setup
No setup — browser_action and code_exec are live by default. Cron schedule via schedule weekly: scrape pricing.

Watchlist alerts (any URL → any event)

Stratam watches a URL or RSS feed for changes and pings you when something matches. Useful for product launches, regulatory filings, blog posts from specific people.

watch https://anthropic.com/news — DM me when a new model is announced
→ monitor_create · file watch + RSS · 1.1sMonitor armed. Polling Anthropic news page every 15 min. Trigger: new article + title contains "Claude" or "model" or "release". I'll DM you the title + link within 30 min of publication. Active monitors: 9.
Setup
Just describe what to watch. Stratam builds the matching monitor in /root/.jarvis/monitors.jsonl and adds it to the R41 polling loop.

Daily intel brief at your wake-up time

Curated morning summary: overnight news in your sectors, key X/Twitter conversations, your inbox status, calendar for the day. All in one Discord DM at the time you set.

→ daily_briefing · 7.8s · 06:00 ET☕ Morning brief, sir. News (3 worth your attention): • Anthropic shipped Sonnet 4.7 — context window now 500K • OpenRouter raised prices on Claude routing by 8% • Hyperliquid hit $5B in TVL milestone last night Inbox: 4 unread, 1 needs reply (Sarah re: expansion). Today: 10am Casey 1:1, 2pm investor update review, 4pm gym (calendar reminder). Markets: BTC -2.1% overnight; ETH flat; your Hyperliquid position +$340.
Setup
brief me at 6am ET every weekday — stores schedule in cron. Customize sources via /app/briefing/config.
For traders

Alerts that don't cry wolf.

Price + funding + open interest · narrative scanning · position monitoring

Every charting tool sends 200 alerts a day. Stratam triggers on combinations — price + funding + open interest + sentiment — and only when multiple signals confirm. Fewer alerts. Higher signal.

Multi-signal price + funding alert

Combine price levels with derivatives data. Get pinged only when several conditions align — not every time price moves 1%.

alert me when ETH funding flips negative on Binance perp AND open interest is rising
→ monitor_create · perp_funding + open_interest · 1.3sMonitor armed sir. Polling every 60s: • Trigger: Binance ETHUSDT funding rate < 0 AND OI 1h Δ > +2% • Notification: Discord DM • Cooldown: 4h between fires (so you don't get spammed if it stays triggered) Last similar setup fired 2 weeks ago, 47% accuracy on next-24h direction. I'll log every trigger to /app/trading/journal.
Setup
Hyperliquid + Binance API keys (read-only) at /app/integrations. No trading permissions unless you explicitly grant them — Stratam is monitoring-only by default.

Portfolio drawdown + liquidation distance

Watches your open positions across exchanges. Pings you when drawdown crosses a threshold OR when liquidation distance closes faster than a set rate.

monitor my hyperliquid positions, alert me if any goes within 15% of liquidation
→ hyperliquid_positions + monitor_create · 2.8sGot it. Current positions: • BTC long 0.4 · entry $63,200 · 67% to liquidation • ETH short 12 · entry $3,140 · 42% to liquidation • SOL long 100 · entry $147 · 81% to liquidation Monitor armed. Alert threshold: 15% to liquidation. Polling every 30s. I'll wake you up.
Setup
Hyperliquid read-only API key. SMS alerts via Twilio for overnight wake-ups (rolling out).

Narrative + social signal scan

Stratam scans X, news feeds, and key Discord servers for emerging narratives. Builds a daily "signal" report — what's gaining attention before it shows up in price.

what's the strongest emerging narrative in crypto this week
→ x_intel + web_search · 11.4sTop narrative gaining attention (78% of relevant high-signal X posts): Decentralized AI compute (BIT, AKT, RNDR) • Mentions in last 7d: +340% • Linked to Anthropic 'BYO compute' rumor + OpenAI Stargate news • Largest mover: AKT (+47% week) • Bear case: heavy insider unlocks Q3 Second narrative: perp DEX rotation (Hyperliquid → dYdX → smaller venues). Volume up 23% week-over-week on smaller venues.
Setup
X API key (read-only). Stratam stores signals in /root/.jarvis/intel/narratives.jsonl; review weekly via /app/intel.
For builders

An engineer who lives in your repo.

Code review · bug investigation · doc generation · deploy automation

Stratam reads your codebase, suggests fixes, runs tests in his sandbox, opens PRs. Self-modifies his own source the same way. Anti-fab catches him if he claims to do something he didn't.

Investigate a production 500

Logs into the production droplet (via webhook trigger or direct ask), reads the error journal, finds the root cause, drafts a fix PR.

investigate the 500 we just got, find the root cause
→ read_file · grep · code_exec · 6.2sFound it. Stack trace at error_journal.jsonl:2843: KeyError: 'currency' in handler.charge_card() line 412 Root cause: Stripe webhook payload schema changed in their March 12 release. The currency field moved from top-level to data.object.currency. Your handler still reads the old path. I drafted a PR fix at fix/stripe-schema-v2 — single 4-line change with a backward-compat fallback. Tests pass in the sandbox. Want me to push?
Setup
GitHub OAuth with PR-write scope at /app/integrations/github. Stratam never force-pushes to main.

Auto-generate API docs from your codebase

Run on commit or on demand. Stratam crawls your handlers, extracts the routes + parameters + return shapes, writes docs to /docs/api.md.

generate API docs for everything in src/routes/
→ read_file × 14 · code_exec (ast parsing) · 9.1sParsed 14 route files, 47 endpoints total. Generated docs at /docs/api.md: ✓ 47 endpoint sections (method + path + params + returns) ✓ Auth requirement matrix ✓ Curl examples for each (regenerated from your test fixtures) ✓ 3 endpoints flagged as undocumented (you ship them but they're not in any handler comment) Diff shipped to docs/auto-api.md. Want me to PR it to main?
Setup
No setup needed — read_file + code_exec are default. Point Stratam at the directory; he handles the AST parse.

Atomic deploy with rollback safety

Stratam doesn't push to prod without parse-check, snapshot, health-check. If anything fails after the deploy, watchdog rolls back to the pre-deploy snapshot within 60s.

deploy the auth refactor branch
→ git_diff + self_modify_code + self_restart · 18.7sDeploying refactor/auth-v2: ✓ Syntax check passed (137 lines changed) ✓ Snapshot saved: /opt/jarvis/.jarvis_self_history/20260517_184211.py ✓ Files SCP'd to /opt/jarvis/ ✓ Container restarted (3.2s) ✓ Health check passed (uptime resumed, 0 errors in last 60s) Done. Watchdog is watching for the next 5 min — auto-rollback if anything goes red.
Setup
Builder tier — bring your own droplet. Set JARVIS_SELF_MODIFY_ALLOWED=1 in .env; Stratam handles the rest.

Ready to put yours to work?

Try the demo (no signup) or join the closed beta for full operator access.

Try the demo Join the waitlist →