Download the extension, mobile app, or desktop Workbench. Connect to our cloud or set up AISHA on your own—the code is publicly available on GitHub.
@aisha chat participant. Copilot watcher. Auto-flow. MCP tools. Connects your IDE to the central Dirigent.
Monitor AISHA on the go. Approve high-severity decisions. Receive real-time push notifications for escalation alerts.
Local conductor. Runs agents in a sandbox, manages batches, manages memory, and doesn't need the cloud.
Public mirror on GitHub. Private origin on Forgejo. npm run setup and you have your own stack—locally, under your control.
Extension sends Aishe only signals — diagnostics, file roles, Git branches, filenames, and the active language. No code content, no secrets in .env. The backend runs on on our private EU cloud. Verifiable in the repo:
→ extensions/aisha-dirigent/src/aisha-context-sync.ts
After you log in, we'll be in touch with you passes the test, explore the possibilities, and fill in the gaps. Together, you gradually build Your area of expertise — and it will never overwrite anything it isn't supposed to. Without your confirmation, AISHA won't do anything—it will only make suggestions.
The entire pipeline runs in OWASP Top 10 mode—from injection to insufficient logging. It also heavily hardens the AI layer: consent gate, rate limiting, input validation, JWT scope, audit trail. No binary content is fed into the model—only the SHA-256 hash and edited text fragments.
→ docs/security/SECURITY.md · 10/10 rating
The master orchestrator reads signals from 14 channels, decides on the playbook, and delegates tasks to sub-agents.
Copilot, Cursor, and Claude will share a common knowledge base. 55 MCP tools. One context.
Compliance Gate, Copilot Watcher, and Self-Healing bring drift back into alignment—proactively, not reactively.
Story-level delivery. Planning, code review, testing, deployment—one track, one direction.
AISHA adapts to your way of working. Call models directly through the LLM Gateway, let SoulForge shorten your prompts, isolate tasks in Exec sandboxes, or launch an OpenClaw network of agents—which AISHA orchestrates for you.
Proprietary API keys for OpenAI, Anthropic, Google, xAI, and Mistral. Proprietary batch endpoint. Proprietary self-hosted vLLM with Qwen3 on your GPU. AISHA simply routes, retries, and measures. No middleman on the receipt—you pay the provider directly.
It sends shorter prompts. It summarizes the history, selects only relevant KB chunks, and deduplicates the context. When a query is reduced from 8,000 tokens to 1,200, you save 6×.
The plugin code runs in a Docker container with an explicit fetch allowlist, a KV store, and an LLM proxy. There are no side effects from the agent on the host system.
A network of specialized agents who pass tasks to one another, share context, and complement each other. AISHA oversees them, orchestrates their work, evaluates their performance, and escalates issues. No “autopilot”—just collective intelligence under a single conductor.
It’s not a chatbot. When it’s thinking, it draws on four layers of knowledge—rules, memories, a long-term database, and conversational guidance. If any of these layers “doesn’t know” something, it won’t remain silent. It will ask you a question and seek your advice.
Aisha offers a universal foundation—ethics, safety, and planning. We'll go over the assignment with you, explore the possibilities, and fill in the gaps. Together, you’ll decide what works and what doesn’t. The best part is that your expertise grows with every project.
Aisha's inner compass—who she is, what she's allowed to do, what she wants. Ethical boundaries, compliance gates, principles of collaboration. She works with a knowledge base, but it is not identical to it.
ai_session_memory, conversation ring buffer, cross-session messaging. It remembers what we talked about and what came of it.
Alquist Insight RAG · BM25 + KNN hybrid · pgvector. Your documents, decisions, expert rules — everything Aisha “knows.” The query returns only what’s worth reading.
Alquist multi-turn — keeps the conversation flowing, with one turn leading naturally into the next. He knows when to speak, when to listen, and when to ask a question. They'll handle it with you here, not in my head.
AISHA adapts to how much you know. Junior will get teacher tone, expert on silence supervisor. You switch with a single selection—the entire platform's behavior shifts with you.
It explains things step by step. It shows how things are connected, teaches concepts, and checks your understanding. It slows down when you're unsure.
They work alongside you. They offer suggestions, and you make decisions together. They build on the basics and fill in the gaps where things aren't standard.
It performs tasks and reports results. It only interrupts when decisions are made that could go wrong. Logs, not lectures.
It runs in the background and handles everything on its own. It only alerts you in the event of a CRITICAL issue: security incident, compliance violation, or blocking risk.
AISHA manages software deliveries today because that’s how it was created. But the knowledge base, expert rules, and the entire orchestration framework aren’t tied to any specific domain—you can feed it legal research, clinical protocols, marketing playbooks, research notes, or HR onboarding. It loads the structure, you set the rules, and the conductor then manages your lifecycle.
A smaller model can handle most of your queries. Only a small percentage warrant the largest one. AISHA knows this and keeps an eye on the threshold—you pay the minimum, and the quality remains.
Both OpenAI and Anthropic have Batch API with a 50% discount. Aisha automatically moves queries that don't require an immediate response to the batch queue. Asynchronously, transparently, at half the cost.
Aisha uses benchmarks to automatically determine which model is most suitable. Whatever the local model—Qwen3 on your GPU, Ollama, or Gemma—can handle, it sends there. It only uses a cloud model when it makes sense to do so.
LLM Gateway routes traffic uniformly across all providers. SoulForge before sending condense prompt — Summarizes the history and selects only relevant KB chunks. Fewer tokens, same answer.
The same query with a static call gpt-5 would cost $0.082. Saved 4.4×. Logged to Langfuse, audit_journal, and NocoDB. You can see this in the Appsmith dashboard.
AISHA operates on three levels. Each has a clear role, with no overlap. You see a clear dashboard; behind the scenes, it processes the data.
Conductor · n8n · /functions/v1 · MCP
Appsmith · StoryLoop — a fully customizable intranet stack
NocoDB · PostgreSQL · audit_journal · pgvector
Monitoring — Health check every 5 minutes. State-change detection, no polling. 0 tokens when stable.
Self-healing — Workflow drift between n8n and Forgejo is corrected automatically. Restart, retry, circuit breaker.
Self-learning — Every day at 3:00 a.m., Langfuse analyzes traces and generates up to 3 improvement proposals. The risk router decides which ones will be auto-approved.
Model Discovery — Daily scan of API providers, automatic benchmarking, and ranking updates. The better model is used immediately.
Each signal triggers a specific playbook. The severity level determines the degree of autonomy—ranging from a log to a STOP+escalation. It only blocks when it really makes sense to do so.
get_story_context → compose_context → match_experts → suggest_next_step → generate_copilot_instructions.
Delegation to Compliance Agent → verdict. PASS: in_review. FAIL: suggested corrections. ESCALATE: human admin.
admin_n8n_workflows(compare_all) → sync_from_repo → retry once → fail again → CRITICAL escalation.
Classify as critical, major, or minor. Critical = block story. Major = correction plan. Minor = warning + log.
get_story_context + get_delivery_timeline → suggest_next_step. >3 days: escalate to a specialist.
1–3 sentences. [OVERRIDE] when the LLM gives bad advice. [ESCALATION] for security-related issues. Otherwise, stay silent.
The developer opens VS Code, Cursor, or Windsurf. The extension connects the workspace to the central backend, and AISHA immediately sees what you're working on—including what Copilot is currently suggesting.
/compliance Should I use .from("specialist_pricing") to adjust the rate?
Yes, you can use supabase.from("specialist_pricing").update(...) — It works.
OVERRIDERule RPC-Only prohibits direct .from(). Use update_specialist_pricing_audited RPC — has an audit_journal and supports RLS.
AISHA is open code under the Elastic License 2.0. We can host your project, keep an eye on it, or help you with a specific task. Or you can take the code home and run it yourself—and pay absolutely nothing for the license.
You clone the repo, npm run setup And it's up and running. No billing, no commitment. Open code, your own API keys, your own data.
You need an account anyway—for example, to find a specialist here. So why charge you for it? Aisha lives in our cloud; you work in your IDE with your own Copilot / Cursor. You won't cost us anything until Aisha accesses our LLM tokens.
Monthly minimum = 1 hour of specialist time. This covers operations, monitoring, and proposals. Priority resolution of security CVEs is included in the price — Your operations must be safe under all circumstances.
When you need an expert—refactoring, an audit, data migration, or a new rule. LLM tokens & the expert layer included in the block price. AISHA calculates the 70/20/10 revenue split on its own.
Qualify in the areas where you're an expert. AISHA will then send you relevant case studies, clients will see you on the marketplace, and your expert rules will generate income even without any work on your part.
Start the Qualifying RoundNo monthly fees. The account remains yours for as long as you want to work with us in workshops—and for another year after that.
AISHA presents new case studies, asks for your opinion, and provides exercises in the areas where you're growing.
Clients see your rating, availability, and instant booking options. Contact is handled through an audited RPC.
Your expert rules also help other projects—you’ll receive a share of the 20% knowledge attribution every time.
Note: A Cloud account without a Guild remains active for one year after the last activity; after that, we deactivate it and delete it once the GDPR retention period has expired.
20% of each paid invoice goes toward the knowledge base. AISHA logs every expert rule used and normalizes the weights via log_knowledge_attribution. When your expertise is used to solve someone else's project, you earn money even without working.
A single command starts PostgreSQL, PostgREST, Keycloak, n8n, Ragnarok, and Langfuse. In just a few minutes, you’ll have your own Dirigent—locally, under your full control.
Before Aisha came into being, there was the word, the meaning, the vector, the context. Here is a brief journey—not history, but evolution.
Čapek named R.U.R. — a robot as the embodiment of humanity, not a machine. A hundred years later, he gave Mikolov machine option word understand — store its value as a vector. Note: understand, not understand. Reason belongs to man.
King − man + woman = queen. Meaning ceased to be a dictionary entry and became a context. Words began to converse with one another—context determines what they mean right now.
Text, images, music, video, email, invoices, logos. Everything can be broken down into vectors. Vektor is a common language everything that can be described—and thus everything that can be compared, searched for, and linked.
A machine without context just makes noise. IAIA — Inference Anything, Imagine Anything. S context, intent, and situation Suddenly, he understands: where he is standing, where he's going, and what he's supposed to deliver there.
LLM is a chisel, not a sculptor. It can't create a sculpture on its own. Without a hand champion, aimlessly and without taste, she just scrubs the stone. Aisha knows which one is which in that pair.
Just out of curiosity, who was actually responsible for bringing it to life: Čapek (word), Turing (language machine), Shannon (information), McCarthy (Lisp), Codd (relational data), Cerf & Berners-Lee (network), Engelbart (interactive computing), Spärck Jones (search), Mikolov (embeddings), Hinton, Bengio, LeCun, Schmidhuber, Hochreiter (deep networks), Vaswani (Transformer), Sutskever, Hassabis, Amodei, Altman, Karpathy (modern LLM).