What AIdeazz AI Lab is — right now
Your production AI co-founder fleet plus a marketing engine that connects discovery → content → leads → measurement. Not a prototype.
| Piece | Role | Where to see it |
|---|---|---|
| Public face | Portfolio, blog, inquiry form | aideazz.xyz/portfolio |
| AI Visibility Audit | Free live API + widget — score any site 0–100 on GEO · AEO · tech SEO (ChatGPT / Perplexity / Claude / Gemini readiness) | aideazz.xyz/api |
| Tech hub | CRM, blog, outreach, performance tracking | CTO AIPA Telegram |
| Marketing radar | Weekly ad-market intelligence on the lab’s seven sellable services — open windows arrive as ready-to-run sales briefs, and CRM outcomes feed back so the radar learns what converts | Atlas live radar |
| CRM spine | All agents feed one HubSpot pipeline | HubSpot Sales Pipeline |
| Measure layer | Website sessions, form leads, deals by campaign | Atlas concept cards (performance block) |
| Sibling products | EspaLuz tutoring, job hunter, social bots, creative AI, daily briefing | Portfolio |
Marketing engine flow (closed loop, July 2026): SEO & discoverability → daily blog → inquiry form with tracking → HubSpot → lead triage → outreach → Atlas detects a market window for a service we sell → sales brief lands in Telegram → outreach goes out → CRM outcome (sent / replied / won) flows back into Atlas → next week’s briefs are smarter
| Status | Reality (July 21, 2026) |
|---|---|
| Loaded | Discovery, content, CRM ingest, triage, Atlas radar on the lab’s seven service lanes, performance bridge, GA4 sync, WhatsApp click tracking, Telegram sales briefs + CRM outcomes feedback (Jul 21) |
| Partial | Conversion — the loop’s first honest read: outreach reply rate ≈ 4% on the visibility-audit lane (24 sends → 1 reply). The engine now measures this per service; beating it is the current game. |
| Next | Showcase package for clients; automated weekly blog from each Atlas snapshot; ads API read |
| Phase | Marketing roadmap | Status |
|---|---|---|
| 1 | Foundation — SEO, analytics, trust signals | Loaded |
| 2 | Content — daily Dev.to blog | Loaded |
| 3 | Attribution + Atlas measure | CRM outcomes loop live (Jul 21) |
| 4 | Outbound (WhatsApp-first prospect play + Atlas briefs) | Live · measured per service |
| 5 | Lead triage | Operational |
| 6 | Client showcase package | Priority |
- Open Atlas — the snapshot refreshes every Monday ~9:15 AM Panama and should show the most recent Monday’s date.
- Open the angle API — live market angle for a service lane, with real CRM outcomes, as JSON. This is the same intelligence the sales briefs use.
- Visit aideazz.xyz/blog — new articles publish on a daily cadence, including posts written from Atlas’s own weekly snapshot.
- Submit the inquiry form on aideazz.xyz/portfolio — you receive a confirmation email when it works (or use the form right on this page, below the go-to-market pipeline).
- Engineers: full runbook in Marketing Engine roadmap on GitHub.
Products & agents
Each row is a shipping capability—what customers or partners touch—with how it runs underneath (Linux services, process supervisor, or serverless). Naming matches the internal resilience matrix without exposing infrastructure coordinates.
| # | Agent | Role (business + ops) | Runtime | Status |
|---|---|---|---|---|
| 01 | EspaLuz WhatsApp | Channel: Spanish tutoring on WhatsApp—conversation, drills, corrections. Runs as a managed Linux service ( espaluz-whatsapp) with automated health checks. |
systemd | ● Live |
| 02 | EspaLuz Telegram | Channel: Same tutoring product on Telegram. Two-layer memory: retrieval + pgvector RAG ( espaluz_rag.py). Service espaluz-familybot. |
systemd | ● Live |
| 03 | EspaLuz Influencer | Brand: Instagram publishing on a disciplined schedule; can spotlight real shipping milestones in consumer-friendly copy. Groq captions + Make.com media handoff. Unit espaluz-influencer. |
systemd | ● Live |
| 04 | Algom Alpha (@reviceva) | Growth: Always-on X presence (education + narrative); folds major releases into the timeline without sounding like raw developer logs. Stream sampling, engagement runner, and account-activity hooks coordinated with the CTO bot for alerts / follow-back. PM2 workers include dragontrade-main and satellite processes. |
PM2 | ● Live |
| 05 | VibeJob Hunter | Product: Autonomous job hunt pipeline—evaluation harness, routing, ATS integrations. Shares codebase with the marketing co-founder agent. Worker vibejobhunter. |
systemd | ● Live |
| 06 | AI Marketing Co-Founder (CMO AIPA) | Revenue narrative: LinkedIn cadence, long-form syndication, CRM hygiene—turns engineering momentum into market-facing proof. Claude + connectors for social; Hunter.io enrichment → HubSpot. Paired FastAPI bridge vibejobhunter-web exposes an internal health route. |
systemd | ● Live |
| 07 | OpenClaw Vibejob Shortlist | UX: Curated job shortlists delivered inside Telegram. Standalone gateway service openclaw-gateway; probed via private health URL on the app host. |
systemd | ● Live |
| 08 | Tech Co-Founder (CTO AIPA) | Control tower: Watches repositories, scores riskier changes, broadcasts milestones to marketing, runs outreach/board workflows. Express orchestrator under PM2 ( cto-aipa), Oracle Autonomous DB via wallet-based TLS—credentials never live in this HTML. |
PM2 | ● Live |
| 08.1 | Sprint Briefing (Sprinter) | Founder ritual: Daily audio briefing synthesized from tasks, notes, and captures. AWS Lambda on a schedule; pulls context through the CTO service over HTTPS with shared-secret auth—no database wallet inside Lambda. |
Lambda | ● Live |
| 09 | Creative Co-Founder (Atuona CCF) | Creative partner: Separate bot persona + public studio site—same reliability envelope as the CTO stack. Single PM2 orchestrator binary; site ships via static edge hosting. |
PM2 | ● Live |
| 10 | Atlas Shifted (Marketing Strategist) | Marketing intelligence: Watches the public ad market daily (9 AM Panama), scores which angle is opening, exports test campaigns, and—since July 2026—pulls real Google Analytics sessions back into a performance ledger so you can see if a test moved traffic. Detect → create → measure loop. Public ad-transparency data only for detection; GA4 for outcomes. Live at atlas.html. |
PM2 | ● Live |
| 11 | AILA | Roadmap: Long-horizon personal orchestration—documented architecture, not yet a standalone production process. Interim coordination fields live in Oracle until AILA ships. |
— | In design |
Reliability & uptime practice
For founders: scheduled probes ask each product whether it still responds. For engineers: one bash driver on the primary Oracle VM runs roughly every five minutes; keep-alive traffic avoids idle reclamation; systemd caps restart storms.
.env change — tested against a golden-set eval before flipping, and instantly reversible. The switch shipped fleet-wide in July 2026, weeks ahead of the deadline. For founders: the AI vendor treadmill is priced into the architecture, not paid for in rebuild weeks.pm2 jlist status onlineGo-to-market automation
When engineering ships something worth talking about, the stack fans it out across LinkedIn, blogs, X, and Instagram—without a human retyping the same story five times. And when a lead comes back in, the same stack answers first.
feat:, launch:, or release: notify the marketing agent. Housekeeping commits (fix:, docs:, chore:, …) stay invisible to customers.Commit detected → CTO AIPA
Push events hit the secured webhook. Groq/Claude review diffs, classify milestones, enqueue pending updates for downstream marketers.
CMO generates + posts
Claude Sonnet copy → Make.com delivery. Zero manual paste.
Bilingual blog publish (EN/ES)
The daily blog publisher ships articles to aideazz.xyz/blog with dev.to crosspost (“Also on Dev.to”). Sliding-window mutex, title dedup, and always-notify Telegram guard against silent double publishes.
Algom Alpha tweet
x-tech-updater.js merges milestones in plain language (Haiku / Groq), guarded against duplicate queue states.
EspaLuz Influencer
Milestone-aware caption + Make.com media pipeline; falls back to standard queue when nothing pending.
Lead Concierge — form to sent reply in minutes
Portfolio inquiries become HubSpot contacts in seconds (server-side push, no cron wait). Make.com wakes Claude to draft a personalized reply—right language, right proof links, concrete first-engagement offer—delivered to Telegram with Send / Edit / Skip buttons. One tap emails the lead from the company domain and logs the sent text to the contact’s CRM timeline. Full audit trail, human approval on every send, response time cut from days to minutes.
Release discipline
Board-friendly translation: we ship like a product company—predictable processes, isolated secrets, verifiable rollouts—even though agents move faster than most teams.
One live checkout per codebase
Eliminates “which folder is prod?” debates; paired bots share code intentionally but never duplicate repos.
Green build, then swap
Pull latest → compile/tests succeed → only then restart supervised processes. Broken artifacts never replace what customers already rely on.
Secrets isolation
Each bot owns its environment file; crypto wallets never touch GitHub; TypeScript strict mode catches sloppy typings before prod.
Crash-proof process registry
Every agent process is registered to auto-start on server boot and auto-restart on failure—no manual babysitting after a power cycle or kernel update.
No silent failures
Crash handlers log before exit so supervisors show why something died; watchdog cadence targets ~5 minute detection.
Verify after deploy
Health signal green, database connectivity logs clean, one real Telegram interaction—all pass before the incident is closed.
Incident response template
For stakeholders: regressions are handled like financial reconciliations—symptoms, compounded causes, fix, proof—so the same automation trap rarely strikes twice.
HubSpot duplicate posting loop
May 10, 2026 — same milestone tweet emitted twice ~6 minutes apart
x-tech-updater.js cycle.posted vs filter on posted_x; mark endpoint keyed on timestamp while older rows used received_at; backlog needed posted_x backfill.
{"ok": true, "pending": [], "total": 0, "held": true} + two full automation cycles without duplication.The engagement loop that never ran
May 25, 2026 — config said “32 engagements/day”; logs said zero cycles had ever completed
grep never matched PM2’s box-drawing table output—so it judged a healthy process dead, forever.pm2 jlist | jq on the process status field instead of grepping rendered text. Process stayed up; the first engagement cycle in the bot’s history fired the same day, with real replies and follows verified from logs.Stack reference
Boring reliability primitives where uptime matters; sharp AI + CRM + social APIs where differentiation matters.
Questions people actually ask
The five questions that come up most, answered plainly — and marked up so AI answer engines can lift them directly.
What is the AIdeazz AI Lab?
A production fleet of eleven AI co-founder agents plus a marketing engine, running 24/7 on a single Oracle VM at zero monthly infrastructure cost. It publishes content daily, captures leads into a CRM, and measures whether campaigns moved the needle rather than reporting vanity metrics.
How does AIdeazz keep AI agents from dying silently?
Every product declares a health check, a restart command and a process name in one resilience config. A watchdog polls those checks and restarts a dead process, and failures surface in Telegram rather than waiting to be noticed. Silent death was the original failure mode, so a service that stops answering is treated as an incident, not a gap in the graph.
Does the marketing engine generate leads, or only traffic?
Inbound inquiries post from the website into Oracle and HubSpot instantly, then a Make scenario drafts a reply that is approved from Telegram before it sends. More than 900 deals and 500 contacts exist in the CRM. Attribution is instrumented end to end with UTM tags, though campaign volume is still low.
How is content optimized for AI search, not just Google?
A 34-check audit engine scores every page for AI crawler access, structured data, answer-readiness and technical foundation. robots.txt explicitly allows 28 AI crawlers including GPTBot, ClaudeBot and PerplexityBot, and llms.txt plus a geo-manifest give answer engines a content map. A weekly citation probe then asks Google AI Overviews, Gemini and OpenAI search whether AIdeazz was actually cited.
Who is this page for?
Business owners who want a plain-language view of what is live, and engineers who want proof. The engineering appendix with repositories, deploy paths, health checks and postmortems lives on GitHub, so this page stays readable and contains no IP addresses, ports or secrets.