Open source3 public repositories
The tools we wish existed.
What we can release, we release — tooling built alongside our production work, under permissive licences. This is a small roster, not a portfolio: it lists what is actually public today.
01 · Projects
What we've released.
Every public repository in the Newron org, with its licence and last activity. Nothing here is listed as maintained that we are not touching.
02 · Why we do it
Some things shouldn't be proprietary.
Our edge is in deployment and custom models — not in hoarding the basics.
Shared evaluation
Honest, reproducible benchmarks make the whole field better. We'd rather compete on results than on secret test sets.
Indian-language tooling
Tooling for Indic OCR and speech is scarce, and most of ours is still customer-specific. Where we can separate it from customer data, releasing it lowers the barrier for everyone building here.
Interop over lock-in
Open schemas for statements and documents would let institutions move data without being trapped by any one vendor. We'd like to publish ours; it isn't public yet.
What we can't open
Customer-trained models, customer data and anything covered by a deployment agreement stay closed. We'd rather say that plainly than imply a bigger public footprint than we have.
03 · Contributing
How to get involved.
Issues and pull requests are welcome on any public repository.
- Start with an issue. Open one describing the bug or proposal before sending a large change, so we can align on approach.
- Check the repository README. Setup, style and test expectations live there; open an issue if anything is missing or out of date.
- Add to the benchmarks. New evaluation cases — especially for Indian languages and document types — are some of the most valuable contributions.
- Sign your commits. We use the Developer Certificate of Origin; a signed-off commit confirms you can contribute the code.
04 · Questions
Common questions.
What licence do you use?
Per project, and it is listed next to each one above: cortex and n00bs are MIT, newron-sdk is Apache-2.0. The LICENSE file in each repository is the authority.
Do you accept external contributions?
Yes. Issues and pull requests are welcome; start with an issue for anything substantial so we can discuss the approach.
Are the production models open?
The shared tooling, schemas and benchmarks are open. Our custom, customer-trained models are not — those are licensed to the customer.
How do I report a security issue?
Please disclose responsibly via our security contact rather than a public issue. See the Security page for details.
Build with us
Use it, improve it, ship it.
Open an issue or send a pull request on anything public. If you're building regulated AI in India, we'd love to compare notes.