Built at Daeda Tech

Daeda Command Center

•active•Software

Tech stack

typescriptreactchart.jscron jobsmcpgsc apiposthog apisqlite

Links

01 /Gallery11 photos

  • 01
  • 02
  • 03
  • 04
  • 05
  • 06
  • 07
  • 08
  • 09
  • 10
  • 11

02 /About

The command center for running Daeda - one internal app where every marketing and business signal lives in one place and the AI has full context. It grew out of a deliberate choice to build an internal OS instead of buying tools, and it replaced a stack of scattered docs, spreadsheets and subscriptions.

How It Works

The loop is capture, file, surface, decide, express, and each area owns one stage. Scheduled fetchers pull from search consoles, site and product analytics, page-speed, CRM, video and the forums, each writing to a single structured store. Every room is a view over that one store.

The Rooms

  • Overview: the morning read - top operating metrics across search, traffic, answer-engine visibility, demos, content and pipeline, with a what-changed feed and a needs-attention list.
  • Work: the desk - a weekly block plan, a worklog of done work, and one ranked next-best-work queue.
  • SEO: a search operating dashboard - performance, health, growth and tracking on live search-console data.
  • AEO: answer-engine visibility - share of voice, AI citations, the prompts we get cited in, and a recommendation queue.
  • Socials: community listening and video tracking, powered by Community Radar.
  • Blog: the writing room - a content pipeline and an editor that writes straight to the real markdown, previewed against the live stylesheet.

Posts

Discussion & feedback

Have questions about this project? Built something similar? Share your thoughts. Comments need a GitHub account.

03 /Related projects

J4 - CONNECT

YOUTUBE
TIKTOK
INSTAGRAM
GITHUB
LINKEDIN
SUBSTACK