Your developer workspace
Scope a local AI setup around your code, files, tools and preferred models. Make the workflow visible and repeatable.
ENGINEHEAD SOFTWARE DEVELOPMENT
Software built
for what
comes next.
Practical software and AI integrations, built around real work.
Meet Niblit, our evolving local intelligence workspace, or bring us a workflow worth improving.
✳ Independent development from South Africa. Built with purpose.
NIBLIT / WORKSPACE01—04
n.CORE
◈ MEMORYcontext that persists
⌘ TOOLSactions with evidence
✳ MODELSlocal or connected
↗ MARKETSdemo integrations
THE IDEA
N / 01One workspace.
A connected feedback loop.
Architecture illustration · not live runtime telemetry
LOCAL-FIRST BY DESIGNMEMORY WITH SOURCESINSPECTABLE TOOL USEOPEN UNDER MIT
01 / OUR PRODUCT — NIBLIT
A workspace with
continuity.
Useful intelligence needs more than a chat box. Niblit connects the model to the work, keeps the evidence, and makes the moving parts visible.
CURRENT DEVELOPER BUILDContext that survives
Context that survives
the conversation.
A persistent memory framework connects a local evidence ledger with Qdrant search. Retrieved passages keep source references and confidence, so stored information can be inspected.
Explore the repository ↗memory / evidenceILLUSTRATIVE VIEW
⌕ Find context from my project
SOURCE-REFERENCED MEMORY
Keep the observation.
Keep where it came from.
source attachedreviewable
THE FEEDBACK LOOP
Observe→Retrieve→Act with permission→Review the outcome
The goal is measurable improvement through evidence. Saving feedback alone does not train a model.
02 / ENGINEHEAD SERVICES
Start with a real workflow.
Make it yours.
Software development and AI integration for developers, independent builders and small teams. Start with a focused pilot, then expand what proves useful.
SETUP & INTEGRATION
Memory for your knowledge
Explore document ingestion, source-backed retrieval and a searchable knowledge layer designed around your material.
A prototype worth testing
Connect a specific workflow to a dashboard and measurable outcomes. Agree the scope and acceptance checks before implementation.
Pilot-led, not one-size-fits-all.
Availability, scope, cost and ongoing support are agreed directly. No automated checkout or subscription is offered here.
03 / BUILT IN THE OPEN
Ambitious direction.
Honest progress.
Niblit is under active development. Here is the distinction between a working integration and what comes next.
CURRENT BUILD
The local toolbox
Desktop workspace, local model conversations, inspectable commands and persistent evidence memory.
Developer preview · setup required DEMO INTEGRATIONS
Market workspace
MT5 demo and Freqtrade dry-run connections for prices, positions and manual simulated order testing.
No promise of profit or validated strategy performance NEXT STAGE
A more aware workspace
Better autonomy, stronger retrieval and future visual event understanding, developed through bounded, observable tests.
Roadmap · not a delivered service capabilityFollow the work. Inspect the code.
Explore Niblit, read the documentation, or open a conversation about a contribution.
A FEW THINGS TO KNOW
Before we build.
Is Niblit a finished operating system?＋
Niblit is an evolving AI runtime and developer workspace. The broader operating-system vision is a development direction, not a claim that it replaces your current OS today.
Does it run locally?＋
The current desktop setup supports local models, tools and memory. Connected model providers and cloud memory are optional integrations with their own setup and costs. The website itself has no access to your PC or Niblit runtime.
What would I be paying for?＋
The source project is MIT-licensed. A service engagement would cover an agreed scope such as setup, integration, customization or support. Pricing and delivery are discussed before work begins.
Can Niblit trade for me?＋
Current demonstrated integrations are for demo and dry-run testing. They do not establish investment performance or a production trading service. Funded deployment needs separate validation, permissions and account-specific controls.
How do I get involved?＋
Visit the GitHub repository for code and documentation. For a pilot, use the enquiry form below to prepare a GitHub issue. You review and submit it yourself; do not include passwords, API keys or private account details.
LET’S MAKE IT USEFUL
Your next idea.
A place to start.
Enginehead Software Development is led by Riyaad, an independent builder in South Africa. Bring a real problem, an existing workflow, or an idea you want to test.
Meet the builder on GitHub ↗