A personal AI assistant that remembers what matters. Talk with KESPA, work through ideas, build projects, share files, and give it context over time. Useful knowledge can be remembered and brought back later, so every conversation does not have to start from zero.
These numbers are pulled from KESPA’s live data, so they update as the system changes. They reflect real usage, research, knowledge activity, and ledger records.
Knowledge promotion activity will appear here.
Training lifecycle activity will appear here.
Canonical proof activity will appear here.
Rankings are based on real KESPA usage, with benchmark and test traffic left out. Only users who choose to make their profile public are shown here.
Can continuously maintained, provenance-preserving external intelligence shift the task-performance / compute frontier of resource-constrained models, and do those gains survive when the reasoning model changes?
Research reports experiments and benchmarks. Trusted Knowledge is maintained evidence-backed intelligence. Technical updates document implementation changes. KESPA does not present one category as another.
KESPA v7.0 introduced a first-class privacy-aware image_edit path after private routing correctly failed closed when no eligible provider could receive the source image. The implementation authorized the local image bridge, added deterministic transparent-background processing, provider fallback strategies, stronger edit lineage/provenance, and safer error handling while keeping control in Admin/brain_config/provider routing and requiring no Brain runtime modification. Production validation remained pending.
What is your purpose?
The verified-intelligence condition recorded 54.22 quality, 1.68 s mean latency, and 0.1085 Wh measured GPU energy. The result is preliminary internal evidence, not universal model superiority.
The homepage reads the canonical KespaAI-Research manifest and keeps a last-known-good snapshot. A temporary repository/sync failure no longer silently turns real research counts into zero.
KESPA is built independently by NexLabs Studio. Contributions and partnerships help cover the real costs behind the project, including compute, research, infrastructure, and ongoing development.
Make a one-time contribution of any amount to help fund continued development, research, and infrastructure.
Support KESPAWe’re open to hardware, compute credits, infrastructure support, research collaboration, and other partnerships that can help KESPA grow.
Partner with usGet in touch for more information about the project, our research, the technology behind KESPA, and where we’re taking it next.
Investor informationThe model is only one part of the system. KESPA keeps its long-term knowledge, memory, evidence, permissions, retrieval, and provenance in layers that can continue working even if the model changes.
New information starts as evidence and candidate claims. From there, it goes through verification, policy checks, conflict handling, indexing, and provenance before it can become trusted knowledge.
KESPA gives the model the context it needs when it needs it, instead of expecting one model to memorize everything.
Personal or private context does not automatically become part of public research, shared knowledge, or the public retrieval system.
When KESPA finds something it does not know, the research system can look for public sources, evaluate the evidence, verify new claims, and package the result for review.
MySQL stores the authoritative data. Chroma handles retrieval and can be rebuilt when needed. NexLedger records tamper-evident proofs for important system events and research records.