Log in Sign up

Threats

A survey of the possible things that could end Blot

There are a number of things that could go wrong. Below are a list of threats to Blot’s business that go beyond being merely made irrelevant by a better competitor.

Payment processing issues

We use Stripe to process 100% of our payments. If Stripe closed our account we would be without revenue.

Solutions:

Hosting provider issues

We use AWS to host the site. If AWS decides something runs afoul of their intricate terms of use, we would be in trouble. What would happen? Well Blot is easy to deploy on a linux server. I would probably move to another provider, say Linode. What would break? Sites with A records pointing to Amazon’s IP address would no longer resolve. Sites with CNAME records pointing to our hostname (blot.im) would continue to work.

I don’t make backups of the data on the system outside AWS. I should really do this, even if it’s only weekly. AWS makes it fairly expensive to move the quanity of data Blot stores, which is one thing I resent about their service (it seems strategic to me).

Solutions:

Cultural issues

We have a policy which means that we allow anything legal on our platform. I suspect that one day, someone will post something that pisses of someone else who’s prominent enough to trigger a pile on against our platform.

Solutions:

Service provider issues

We could get sued by a well-resourced customer, or someone who reads a customer’s site.

Solutions:

Personnel issues

Blot’s bus factor is still 1 — if I get hit by a bus the show stops. Since the source code is public, it would be possible for those who liked Blot to keep it going on a different server, but coordinating the switch might be tough.

Solutions: