ABOUT Wizkers.io

Wizkers was created by Edouard Lafargue, in Palo Alto, California. Here is the story of the project.  

 

Q: Why did you create Wizkers.io?

Ed: I created out of frustration. Frustration that super powerful electronics tools like my multimeter could not be used to their full potential. And frustration that many great open source frameworks are just not user friendly:

  • Too many lab instruments have no decent computer utilities even though they have great connectivity. Those utilities are usually less than user-friendly, Windows-only, and poorly supported. Of course, there are industrial solutions like Labview, but those are often overkill and complex for day to day use.
  • It is becoming easier and easier to create and use many small and not-so-small sensors that generate data, but finding good ways to record, visualize and analyze their output, and remotely configure and control them with an engaging interface is often an afterthought.
  • Most IoT services are all about 'dumb' sensors and easy and free APIs, but at the cost of a completely closed backend and limited control on your data once it is sent over. Basically, you are only getting access to half of the infrastructure, and the arguably most critical part is outside of your control. But there are many situations where you want to be able to deploy your own infrastructure without having to rely on a third party, especially if you are not deploying millions of sensors, or you cannot do 24/7 connectivity for some reason.

Another issue we have experienced many times over the last few years, is that most IoT startups cannot provide any kind of continuity and stability for a project: from Pinocc.io to Pachube, Spark.io, Helium.com, etc, most of those companies tend to review and modify their business model every couple of months, and put any project that relies on them at great risk.

Wizkers.io solves all this issues with one elegant framework: In a nutshell, Wizkers is both the missing link between your sensors, your instruments and the Cloud, as well as the missing universal utility for scientific instruments which works on any OS and any computer. 

Q: What does Wizkers stand for?

Ed: This project is called ‘Wizkers’, after the whiskers that allow felines to enhance their perception of the world around them and “Wiz” for “Wizard”.

Q: How do you see it evolving?

Ed: I have been excited to integrate Wizkers.io with many great products from Medcom, Safecast, Elecraft, Fried Circuits and I see more and more request for it. Thanks to its plugin system, Wizker.io can be extended to support any instrument. So as a next step I can see more devices being included in the standard distribution over time. You can help too, Wizkers.io is Open Source!

Wizkers.io connected to Safecast counter in freezing conditions