CES 2013: Transporter Lets You Create Your Own Off-site Cloud for $200

Startup company’s clever technology, styling, and naming made it a Kickstarter success

1 min read
CES 2013: Transporter Lets You Create Your Own Off-site Cloud for $200

Strolling the aisles of Digital Experience, an event for CES press attendees held last night in Las Vegas, there were lots of shiny, colorful, cute, or sleek objects on the hundred-plus tables, with eager entrepreneurs, designers, and marketers ready to convince me that their product/software/service is the next big thing. A fair number were fairly easy to walk by. But the simple silver cones on one table, however, drew me like a magnet. I loved the industrial design and the name, Transporter, seemed to fit the design. I hoped that whatever the heck this gizmo was made as much sense as its look and name.

Geoff Barrall, Transporter founder, convinced me that it did. The Transporter is essentially a cloud in a cone; pop it somewhere it can connect to the Internet (preferably in a different building than your computer) and it acts as offsite backup or file sharing device, requiring no setup or computer connection. Barrall first envisioned his customers as lawyers and other professionals who don’t want to entrust confidential information to a commercial cloud, but at $200 for a bring-your-own-drive version or $300 for a 1terabyte version, sees the product catching on with consumers who want off-cloud storage, or to share files within a small group.

Barrall said his campaign on Kickstarter, the micro funding service, hit 200 percent of its milestone yesterday, and the company will start shipping Transporters by the end of the month.

Follow me on Twitter @TeklaPerry



The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less