dweet.io is simple publishing and subscribing for machines, sensors, devices, robots, and gadgets (we just call them things). We call published messages ‘dweets’. It’s helpful to think of dweet.io as a Twitter for things, in fact.
We assign each thing a unique thing name (or you can assign your own if it’s available). Then a thing may be subscribed to, which is analogous to following someone in twitter.
dweet.io enables your machine and sensor data to become easily accessible through a web based RESTful API, allowing you to quickly make apps or simply share data. Some examples of data that can be dweeted:
We believe that simplicity is the purest form of reliability and performance. dweet.io was built from day one for commercial and Enterprise deployments— because it's so simple, there is less to slow it down and less to break.
If you want even greater reliability, Email us to find out about our dedicated instances and SLA's.
A dweet payload can be up to 2,000 characters. For comparison, a tweet on Twitter has a 140 character limit.
By default, dweets are public. You can make dweets private by purchasing a lock for your thing. Locks are applied to thing names. They allow you to protect and reserve your thing so that only people (and apps, machines, etc) with special keys can access its dweets. Once you lock a thing, the name of that thing cannot be used by anyone else.
dweet is free to use. If you want to reserve a thing name and keep your dweets private, it’s $1.99 per lock per month.
Each lock costs $1.99, but they will all show up as a single line item on your credit card bill every month for the total combined amount.
We only hold a thing’s last 5 dweets for up to 24HRs unless it's a locked dweet. If you lock your dweets, each dweet is stored for 30 days.
We're currently beta testing 30 days of storage per locked dweet. We plan on rolling out more storage options and we'd love to learn about your needs. Just get in touch!