Developers
-
Power your apps
-
Forecasting Resources
Why?
- More accurate than in-house code.
- Less hassle, less maintenance.
- Fully scalable.
Open source projects
At Lokad, we typically release as open source projects that happen not to be tightly related to our core forecasting technology. Those tools and components are critical for us, we hope they will benefit to the community too.
Tier 1 projects, in production at Lokad, actively developed and maintained:
- Lokad.Cloud - .NET O/C mapper (object to cloud) for Windows Azure.
- Lokad.CQRS - Command-Query Responsibility Segregation for Windows Azure.
Tier 2 projects in production at Lokad, but no company commitment for maintenance:
Quasi Lokad open source projects
Those projects have not been developed by Lokad, but rather by individuals who happened to end-up in the Lokad team at some point. Lokad is not necessarily the lead contributor in those projects, but we keep a vivid interest in them.
- Math.NET - Mathematical library written in C#/.NET.
- Autofac - An addictive .NET IoC container.
- ScrewTurn Wiki - ASP.NET Wiki (Lokad.com is hosted on STW).
Products developed by Lokad as open source are released under the
BSD license. The BSD license is compatible with both open and closed-source applications. Integrating a forecasting technology has never been easier.
Our projects are now primarily hosted on
GitHub, but older projects can still be found on
Google Code.
What people say
From a developer standpoint, we found that the Lokad API was very well
documented and easy to use. The Lokad team was also extremely
responsive to any questions we had. Most importantly, we were able to
develop a
Lokad plugin for our data browser in very short order.
Jeff Engel,
Kirix CorporationOpen-source strategy
Our intellectual property (IP) strategy is simple: we release as open source blocks that have a lot of potential for reuse while we keep private the very core of our technology. By doing so, we benefit from community feedback and exposure. It drives us to produce leaner and more reliable blocks that we leverage to deliver better services. IP loss is minimal because reuseable blocks are bound to be redeveloped by dozens of companies anyway, and are merely increasing the entry barrier for our competitors by a few inches at best. Instead, by making those blocks accessible, it gives us an edge to focus on the core: parts both extremely specific to our business and truly hard to reproduce.
Joannes Vermorel, Lokad, Founder