Releases: Context-Engine-AI/Context-Engine
v3.0.1
v3.0.0
What's Changed
- Feature/docker compose optimizations by @chris-stinemetz in #206
- Bubble bullshit by @m1rl0k in #205
- Normalize 'under' path handling and add remote embedding support by @m1rl0k in #209
- Migrate to uv for Python dependency management by @m1rl0k in #208
- Memory fix by @m1rl0k in #211
- Memory fix by @m1rl0k in #212
Full Changelog: 2.4.0...v3.0.0
Licensing Update: Protecting Context-Engine While Staying Open
We're updating the Context-Engine license from BUSL-1.1 to the Context-Engine Source Available License 1.0, effective
immediately.
Why the change
Over the past several months, we've seen multiple instances of our code being lifted, lightly refactored, and repackaged as
"new" products — sometimes within days of a release. This isn't innovation. It's extraction, and it's a growing pattern across
the AI tooling space.
We built Context-Engine in the open because we believe developers deserve to see how the tools they depend on actually work.
That belief hasn't changed. But we also need to protect the project — and the community around it — from actors who contribute
nothing back while profiting from the work.
What's changing
For most users, nothing changes. You can still:
- Use Context-Engine freely for personal or internal business use
- Read, audit, and understand every line of code
- Modify the software for your own needs
- Self-host on your own infrastructure
What's now explicitly restricted:
- Taking Context-Engine and offering it (or a reworked version of it) as a competing code search or code intelligence service to
third parties - Redistributing modified versions outside the official project
Any modifications contributed back are owned by the project, ensuring the codebase stays unified and doesn't fragment into
closed forks that undercut the original.
What's NOT changing
We are not closing the repo. We are not going the route others in this space have taken — pulling source code behind closed
doors, killing free tiers, or locking everything behind enterprise sales calls. The code stays visible. The core stays free to
use.
We believe transparency and protection aren't mutually exclusive. You shouldn't have to choose between trusting a tool and being
able to inspect it.
Premium features
Advanced capabilities like the Neo4j Knowledge Graph plugin continue to require a commercial license for production and
commercial use. The core Qdrant-based functionality remains fully available under the free license.
Questions?
If you have questions about how this affects your use case, reach out directly at john@context-engine.ai. We're happy to
clarify.
Contributors
Assets 3
2.4.0
What's Changed
- Add CAST+ and SOSC chunking strategies by @m1rl0k in #194
- Chunk by @m1rl0k in #195
- Add tree cache to ASTAnalyzer and optimize vector projection by @m1rl0k in #196
- Helm by @m1rl0k in #198
- refactor: optimize Docker Compose with YAML anchors and aliases by @chris-stinemetz in #197
- Fix duplicate mapping keys in docker-compose.yml by @LivioGama in #199
- Bubble bullshit by @m1rl0k in #200
- Bubble bullshit by @m1rl0k in #201
- Add Helm chart with production-scale templates by @m1rl0k in #202
- Improve collection handling and hashing consistency by @m1rl0k in #203
- Update qdrant.py by @m1rl0k in #204
New Contributors
- @LivioGama made their first contribution in #199
Full Changelog: v2.3.0...2.4.0
Contributors
Assets 3
v2.3.0
What's Changed
- Improve symbol matching in graph queries and enforce JSON output by @m1rl0k in #189
- Add resource limits and cleanup to bridge and extension by @m1rl0k in #190
- Cleanup by @m1rl0k in #191
- admin: Add graph collection lifecycle support and improve admin logging by @voarsh2 in #192
- Update vicreg entropy by @m1rl0k in #193
- Modularize extension, watchdog upload client, Antigravity MCP config writing by @voarsh2 in #131
Full Changelog: v2.2.8...v2.3.0
Contributors
Assets 3
v2.2.8
Contributors
Assets 3
v2.2.7
Contributors
Assets 3
v2.2.6
Full Changelog: v2.2.5...v2.2.6
v2.2.5
What's Changed
- feat: Add VS Code Extension button to landing page by @chris-stinemetz in #182
- Add initial Context-Engine CLI implementation by @m1rl0k in #183
- Neo4j graph backend by @m1rl0k in #177
Full Changelog: v2.2.4...v2.2.5
Contributors
Assets 3
v2.2.4
What's Changed
- feat: update hero icon from BotOff to Sparkles by @chris-stinemetz in #176
- feat: Add contact page with enhanced form styling and Formspree integ… by @chris-stinemetz in #178
- Dense by @m1rl0k in #170
Full Changelog: v2.2.3...v2.2.4
Contributors
Assets 3
License Update (BUSL 1.1)
Context-Engine is now licensed under the Business Source License (BUSL) 1.1.
We’re making this change to protect the project while we continue investing significant time and resources into building Context-Engine into the best possible retrieval + code intelligence stack. This licensing model keeps the project broadly usable for individuals and organizations, while preventing a specific class of commercial exploitation: turning Context-Engine into a competing hosted product.
What you can do
You can:
• Use Context-Engine in production for your own internal needs (including commercial use).
• Self-host it, run it on your infrastructure, and integrate it into your workflows.
• Copy, modify, and redistribute the code (including as part of your internal platform).
What you cannot do (without a commercial license)
You cannot:
• Offer Context-Engine as part of a commercial Code Search / Code Intelligence Service where third parties access its functionality as a hosted or managed service (i.e., “we host Context-Engine for customers”).
In plain terms: use it for your team/company = yes. Sell it as a hosted product to others = not without a commercial license.
What changes in 2030
On January 10, 2030, the project will automatically convert to:
• GPL-2.0-or-later
So the BUSL restriction is time-limited by design.
Why we chose this
Open source is a spectrum, and we want Context-Engine to remain widely accessible while ensuring that companies don’t take the project, wrap it in a hosted UI, and profit from it without contributing back—especially while we’re still in heavy R&D and scaling phase.
Need a commercial license?
If you’re building a hosted/managed code search or code intelligence offering and want to use Context-Engine, reach out and we’ll make it easy to do the right thing.