Pinned Tweet
Why pay for the same reasoning twice?
Most AI systems call an LLM every time β even when the work has already been understood and validated.
KORA takes a different approach:
New work learns. Known work runs.
π€ Made with AI
KORA Doctor tells you where to cut it.
Built at Krako. Open source on top of AUDR.
AI agents are making far more model calls than they need to.
KORA Doctor finds where that waste is happening.
Built at Krako. Open source on top of AUDR.
Inference should be earned, not assumed.
github.com/Krako-Labs/kora-dβ¦
Measure β diagnose β eliminate unnecessary inference.
AI agents make far more model calls than they need.
@cbkrish and @chargebeeβs AUDR tell you what an agent used and what it cost.
I built KORA Doctor to answer the next question:
Which LLM calls should disappear?
OSS: github.com/Krako-Labs/kora-dβ¦
The goal isnβt to replace models.
Frontier models. Specialized models. Local models. Tools. Rules.
The more important question is:
Does this step need inference at all?
π€ Made with AI
We call this deterministic-first AI execution.
Determine what you can. Generate what you must.
Full post:
medium.com/@krako_cloud/run-β¦
KORA:
github.com/Krako-Labs/KORA
A 12-step agent workflow.
**0 provider calls.**
KORA's offline Agent Workflow Optimization example routes:
β 4 deterministic
β 2 cache hits
β 3 tool-needed
β 3 provider-needed
β 0 actual provider calls
It's small, reproducible, and easy to extend.
Developers: run it, inspect the routing logic, and contribute.
π github.com/Krako-Labs/KORA/tβ¦
#OpenSource #AI #KORA
12-step agent workflow. Only 3 steps actually needed the model.
KORA routes classification, validation, transforms, and policy checks to deterministic handlers β cache reuse and tool-needed steps handled separately. Fully offline, reproducible:
python3 examples/agent_workflow_optimization/run.py
Open source, contributors welcome π github.com/Krako-Labs/KORA
Ran 7 RAG queries through KORA. Zero hit the model.
2 answered deterministically, 1 from cache, 2 flagged retrieval-needed, 2 provider-needed β but 0 provider calls actually made.
Offline, no API key, fully reproducible:
python3 examples/rag_routing/run.py
Open source, contributors welcome π github.com/Krako-Labs/KORA
Every AI request has a tradeoff.
Should it optimize for:
π° Cost
β‘ Speed
π― Correctness
Not every task needs an LLM.
Use deterministic logic where possible.
Escalate only when reasoning adds value.
How do you balance the tradeoff?
#AI #LLM #SystemDesign #OpenSource #KORA
Every merged PR makes open source stronger.
You don't need to build a huge feature to contribute.
Start with:
β’ Docs
β’ Bug fixes
β’ Reviews
β’ Examples
Your first contribution could help hundreds of developers.
Join KORA:
github.com/Krako-Labs/KORA
#OpenSource #GitHub #BuildInPublic #KORA
The fastest way to understand an open source project?
Read the README.
KORA's README covers:
β Architecture
β Deterministic routing
β Request flow
β Quick start
Good docs are part of the product.
π github.com/Krako-Labs/KORA
#OpenSource #Documentation #GitHub #KORA
Not every request needs an LLM.
Use deterministic logic for:
β’ Validation
β’ Business rules
β’ Routing
β’ Cache
β’ Permissions
β’ APIs
Call the model only when reasoning is required.
That's the philosophy behind KORA.
What would you never send to an LLM?
#AI #LLM #OpenSource #SoftwareArchitecture #KORA
Small bug. Big improvement.
We refined KORA's retry behavior to make execution more reliable.
β
Retry recoverable failures
β
Avoid duplicate execution
β
Preserve deterministic routing
β
Reduce unnecessary compute
Read the PR:
github.com/Krako-Labs/KORA
#OpenSource #AI #BuildInPublic #DeveloperTools #KORA
AI latency isn't just model inference.
Every request spends time in:
β Validation
β Routing
β Retrieval
β Tools
β LLM
β Response
Measure every stage before optimizing.
See the benchmarks and reproduce them yourself.
github.com/Krako-Labs/KORA
#AI #Performance #OpenSource #LLM #KORA
Most AI apps call an LLM first.
What if that was the last step instead?
Validate β Route β Cache β Tools β Retrieval β LLM (only when needed)
Smarter routing means lower costs, faster responses, and more predictable AI systems.
That's the philosophy behind KORA.
β Explore the project:
github.com/Krako-Labs/KORA
#AI #OpenSource #LLM #DeveloperTools #BuildInPublic #KORA
Weekly KORA OSS Roundup π
This week:
β’ New commits
β’ Docs improved
β’ Architecture updates
β’ Bug fixes
β’ More deterministic routing
Building AI infrastructure in the open.
β Star the repo:
github.com/Krako-Labs/KORA
#OpenSource #GitHub #AI #BuildInPublic #KORA
Every AI request shouldn't go straight to an LLM.
KORA's Dispatcher decides the best execution path first:
β Logic
β Cache
β Tools
β Retrieval
β LLM (only if needed)
Deterministic routing = lower cost + better reliability.
Read the architecture:
github.com/Krako-Labs/KORA
#AI #OpenSource #LLM #KORA
AI failures shouldn't be mystery logs.
KORA publishes every routing failure as structured JSON with validation results, execution metadata, and failure reasons.
Debug faster.
Build reliable AI.
GitHub:
github.com/Krako-Labs/KORA
#AI #LLM #OpenSource #KORA
βοΈ Sunday is for builders.
Join the Krako community to learn, build, and contribute with developers from around the world.
π¬ Discord discord.gg/G6yea8XV
βοΈ Telegram t.me/+ISn5ykcIBj0zODE0
πΌ LinkedIn linkedin.com/company/krakolaβ¦
One community. One mission. Build the future of decentralized AI.

















