Jidoka HQ,
for focused operations
A private operations workspace for Jidoka Labs, paired with public marketing pages and a practical path toward CRM, files, agents, and Slack.
Built for internal client operations
Jidoka HQ keeps the app focused on people, projects, files, and practical AI support.
Internal authentication
Email/password auth, confirmation, password reset, and session persistence stay available for invited internal users.
Client project tracking
The CRM starts light: client projects, relationships, notes, follow-ups, and a services-oriented pipeline.
Single workspace
The app is moving away from tenant switching and toward one Jidoka Labs operational boundary.
Team notifications
In-app notifications and email preferences remain available for internal workflow events.
Admin tools
User management, audit trails, feedback, content, changelog, and internal dashboards stay available.
Agent-ready foundation
OpenAI-first chat, pgvector search, private files, and Slack can build on the existing Phoenix foundation.
From template to operations foundation
The current milestone narrows the app toward Jidoka Labs' internal operating model.
What Jidoka HQ is optimizing for
“Projects, relationships, notes, and follow-ups should be quick to capture and easy to revisit.”
“People join by invitation and work inside one operational boundary.”
“Files are private by default and useful for internal memory, search, and agent context.”
“Start with inexpensive OpenAI defaults, then add optional providers only where they help.”
“One internal workspace is enough; messaging should connect the team to the app without ceremony.”
“Local, Docker, and Fly environments should stay boring and reproducible.”
“Projects, relationships, notes, and follow-ups should be quick to capture and easy to revisit.”
“People join by invitation and work inside one operational boundary.”
“Files are private by default and useful for internal memory, search, and agent context.”
“Start with inexpensive OpenAI defaults, then add optional providers only where they help.”
“One internal workspace is enough; messaging should connect the team to the app without ceremony.”
“Local, Docker, and Fly environments should stay boring and reproducible.”
Questions?
Here are the ones we get most often.
Internal users join by invitation. Customer-facing marketing pages remain public.
It is for lightweight relationship tracking, client projects, notes, and a simple services pipeline.
No. The file direction is private by default for internal reference and future retrieval.
Ash domains, CRM resources, private files, pgvector, OpenAI-first agents, and Slack integration are planned as separate epics.
Get notified about updates
We send a short email when we ship new features. No spam, no marketing fluff.
No spam. Unsubscribe anytime.
Build the Jidoka Labs operating layer
Jidoka HQ is the private workspace behind public Jidoka Labs pages.