When Can I Run blist Locally?

Never. I’m serious. I know the customer is always right. Well not this time. blist is delivered as a service because that’s where it makes sense to run it - for you - not just for us.

A number of people have asked about our plans to let you install blist and run it locally. That’s not going to happen. Data wants to be shared. It wants to be accessible from wherever you are. It wants to be accessible from a multitude of devices. It wants to be accessible programmatically. For those things to happen, data needs to be “in the cloud” as they say.

Obviously there isn’t really a cloud. The Internet isn’t a network of arteries and veins in which data builds up like plaque. Companies like blist choose to offer their services via the Internet.

We offer blist as a service in part because it helps us too. It lowers our support costs by ensuring that everyone is using the most current version of our software. It lowers our development costs because we develop for exactly one platform - the one we run on our servers. It lowers our operating costs in a multitude of ways.

But more importantly we offer blist as a service for a major philosophical reason. blist wants to democratize working with data by empowering mainstream users - ordinary people - to organize data without relying on a database administrator (DBA).

Think about how mainstream users now draw diagrams with Visio and make presentations with PowerPoint. Those functions used to be performed centrally by specialists, much like data is still organized by a specialist - a DBA.

If blist is going to succeed at democratizing working with data, we have to eliminate the two dependencies that keep you beholden to the DBA. First, we have to dramatically improve the user experience of working with data so that you can organize it yourself. Second, we have to relieve you of the operational burden of keeping the database running.

In addition to designing schemas, DBA’s fix block corruption. They install software patches. They perform backups and restorations. DBAs are constantly monitoring, tuning and tweaking the database to keep it running optimally. I call it the “muck” of running a database.

By moving the database to the cloud, there’s no local database that you need to keep running. There’s no muck.

We believe breakthrough innovations in usability and freeing you of the operational burden of running a database will pave the way to democratizing working with data. It’s our belief. It’s our mission.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
/

8 Responses to “ When Can I Run blist Locally? ”

[...] did nothing but smile when I read the latest post from Kevin over at blist - titled “When can I run blist locally?”: ” Never. I’m [...]


Do you consider allowing remote access to blist databases from locally running clients? Using some webservice/REST protocols?


Yes, I agree with you, but …

With all those startups who knows who will be around in a years time. Maybe you don’t make it, maybe someone else buys you.

And when i have an app running locally, i know i can run that app in a long time to come.

So there is a reason for wanting something locally ;-)


Erwin — blist allows you to export your data to a CSV. If blist were to go under, there will always be a host of alternatives that accept CSV as an input.

I think a stronger argument for running the application locally is that we are seeing in the marketplace that mid-size to large companies do not desire storage in the cloud as strongly as the internet press might have us believe. Obviously blist is targeted at individuals and smaller companies, but they too may have issues with having their data stored in the cloud, especially if blist encounters any operational or security related issues in the future. Time will tell how quickly and deeply companies adopt service related offerings — generally speaking I think we are in an early stage of business adoption of SaaS.


Going open source hasn’t hurt WordPress - in fact the WordPress.com hosted service has made blogging super easy and was only really afforded by the popularity of the WordPress platform as an open source tool. So there are potential benefits (how does a worldwide army of hacker evangelists sound?!), but it seems like it isn’t the right approach for Blist for the time being. And you would inevitably get more comparisons to MySQL et al, even though it probably wouldn’t be appropriate…


[...] an intuitive appeal to how they think about what they’re doing. And Kevin’s next most recent post reminded me not a little of Hillel’s talk last night — (paraphrasing) We’re here [...]


I agree with the “software as service” approach. I’d stick to MS Office if I needed something else. But how about implementing some offline browser mode, for example via Google Gears? Zoho Office and Google Docs are doing it, I believe.


Working DoD projects last four years in highly secure environment, could have used BLIST and built for myself a 100% solution that cost us $1M+ to arrive at a 20% solution over that time. Too bad it can’t run locally.


Something to say?