TL;DR — Epic Tech AI is a full AI operating system: multi-agent orchestration, sandboxed worktrees, projects, creative studio, workflows, memory fabric, Reflex phone commands, connector marketplace, credits ledger, and a Next.js control center. Runs fully offline with a mock model; connect Anthropic / OpenAI / Google / xAI / Groq / OpenRouter / Ollama via the vault.

Core engine is based on Iron Jarvis (credit: RealDealCPA-VR). Product brand and commerce layer: Epic Tech AI.

Platform: Windows desktop installer + from-source on Windows/macOS/Linux (uv + npm).

Brand / demo audio lives in assets/audio/.

Why some players fail on GitHub: README markdown strips <audio> tags, and raw.githubusercontent.com often forces download instead of stream.
Use the jsDelivr links below (streamable) or the dual player page.

High-energy electronic club instrumental (synths, punchy drums, ~128 BPM). No vocals.

▶ Open dual player (both tracks)
▶ Stream / play Track 1 (MP3)
Repo file · Download

Club electronic with a rhythmic vocal hook (“Dale, le le le…”).

▶ Stream / play Track 2 (MP3)
Repo file · Download

Notes: assets/audio/README.md

• OS, not a chatbot — Supervisor → specialist subagents in isolated workspaces.
• You stay in control — Fail-closed permissions; git review never auto-merges.
• It remembers — Layered memory, LTM, Memory Fabric, lessons that improve over time.
• Phone-ready — Telegram / Slack / Discord channels + Reflex /commands.
• Monetizable — Credits ledger, Stripe checkout hooks, usage metering (keys never hardcoded).
• Local-first — SQLite by default; secrets in an encrypted vault; network optional.

Never hardcode API keys in source, commits, or chat.

# After filling .env with YOUR keys (not committed):
uv run python scripts/load_env_to_vault.py   # prints names + lengths only

Full policy: docs/TOKEN-POLICY.md.

Prerequisites: Python 3.12+, uv, Node 20+ (includes npm), git.

git clone https://github.com/Sm0k367/epic-iron-jarvis.git
cd epic-iron-jarvis
uv run ironjarvis doctor          # or: uv run epic doctor
uv sync --extra dev
cd dashboard; npm install; npm run build; cd ..
uv run ironjarvis up             # daemon :8787 + dashboard :3000

Two terminals: uv run ironjarvis serve + cd dashboard && npm start.

Desktop window over source: cd desktop && npm install && npm start.

uv run ironjarvis demo           # offline end-to-end
uv run pytest -q                 # offline test suite

CLI aliases: ironjarvis and epic (same app).

Build from this repo:

npm --prefix desktop run dist:full
# → desktop/release/… Setup … .exe

Published releases (if any) live on this repo’s Releases. Upstream Iron Jarvis installers may differ in branding.

Closing the window minimizes to tray so schedules / webhooks / TG keep running. Quit from the tray menu to fully stop.

# Preferred (Epic Tech AI)
setx EPIC_HOME "$env:USERPROFILE\.epic-tech"
# Still supported
setx IRONJARVIS_HOME "$env:USERPROFILE\.ironjarvis"

Unset → per-project <cwd>/.ironjarvis isolation.

Dashboard → Connections

CLI:

uv run ironjarvis connect xai <paste-key-in-terminal-only>
# Prefer: put key in .env, then load_env_to_vault.py

Never put real keys in README, issues, or committed files.

Full setup: docs/TELEGRAM.md (BotFather → Channels → allowlist).

Dashboard → Channels — type telegram, bot token, chat id, Enable two-way = true, Allowlist = your user id.

Also: docs/REFLEX.md.

Defaults keep local free: billing off; mock/Ollama do not burn credits.

Credit packs (dev catalog): credits_100 / credits_500 / credits_2000 — Stripe Price IDs via STRIPE_PRICE_CREDITS_* env vars (never hardcode secret keys).

See DEPLOY.md and deploy/. Docker:

docker compose up

Before public exposure: set IRONJARVIS_TOKEN, HTTPS, tight CORS, persist state volume, keep computer-use off unless isolated.

Recover: doctor · repair · backup · restore · rollback · reset-config

CLI: init · serve · up · run · demo · cancel · rerun · doctor · repair · backup · restore · connect · secrets · …

Dashboard (Next.js)  ──REST + WebSocket──►  Daemon (FastAPI)
                                              │
   Orchestrator · Agents · Tools · Permissions · Sandbox
   Providers (xAI/Groq/…) · Connections vault · Router
   Memory Fabric · LTM · Projects · Creative · Reflex
   Billing ledger · Channels (TG) · Workflows · Schedules
                  SQLite (WAL) under .ironjarvis / EPIC_HOME

src/iron_jarvis/
  brand.py          Epic Tech AI identity strings
  billing/          credits ledger + Stripe helpers
  daemon/routes/    REST domains (incl. billing)
  reflex/           phone commands + ambient rules
  providers/        LLM adapters (xAI, Groq, …)
  connectors/       marketplace catalog
  projects/ creative/ memory/ comm/ …
dashboard/          Next.js control center

• Local-first state; secrets Fernet-encrypted; agents never read secret values.
• Inbound TG: opt-in, allowlist, private chat only.
• Stripe / provider keys: env or vault only — see TOKEN-POLICY.
• No auto-merge of agent code changes.

uv run ironjarvis doctor
uv run ironjarvis demo
uv run python -m pytest tests/test_billing_ledger.py -q
uv run pytest -q

Full policy pack lives in legal/ and in the dashboard at /legal.

Contact: [email protected] · @EpicTechAI

Policies are for transparency and operations; they are not personalized legal advice.