Could this be the perfect blog platform for Japan? Could this be the perfect blog platform for Japan?



There are so many ways for people to start a blog these days. The recent trend of ‘static’ blog services like and Ghost are refreshing, because for a personal or casual blog, there really shouldn’t be any reason that you must have your own server running a database [1]. Dropbox lets is publish to the web, and a solution like Calepin (for example) can take advantage of that, serving your blog’s files from there.

The idea behind is similar. The brainchild of Vancouver-based Input Logic, it uses Evernote to post content to your blog, letting users choose between a number of wonderful design templates as well. The startup is off to a good start, having joined Evernote’s accelerator class having won the company’s Devcup this year. To date, I’m told there are 21,000 people blogging with Postachio so far.

The big advantage for a service like this is that it enlists users by finding them on a platform they already use. They already live in Evernote, and can easily publish to Postachio just by adding a note with the tag ‘published’ to a specified Evernote notebook.

One of Postachio’s many themes, Apex

Big in Japan

Shawn pitches at demo day
Shawn pitches at demo day

About 20% of Evernote’s users (and about 30% of its revenue) come from Japan. Docomo, of course, was an early investor in Evernote [2], and has promoted Evernote Premium to its users. So the ties to Japan are already in place for Postachio to make this sort of overseas jump. So naturally, I was curious to see if the Postachio had any plans to push their blogging service in the country. Co-founder and designer Shawn Adrian explained a little their plans for the next year [3]:

We plan to internationalize, and a Japanese version is in the works. […] We’re going really dig in and improve our themes and the community around them. We’re also launching new social features to help users build their audience, and tools for pro bloggers and companies.

I understand the team has already met some representatives from Docomo Ventures in Silicon Valley, and I expect that whenever a localized version is ready, that it would be very well received here.

The team is also thinking to integrate other platforms too, letting people publish from just about anywhere. For me, I like the possibilities of publishing a Markdown note (Postachio does support Markdown) via Evernote’s publish-over-email function, sending from the mobile Drafts app on iOS.

Evernote's APAC GM Troy Malone users Postachio
Evernote’s APAC GM Troy Malone users Postachio

Static blogs are very trendy these days, but the degree of difficulty for many solutions like Jekyll or Pelican, or even the aforementioned Scriptogram, can be difficult for an average user to wrap their head around. Postachio, for someone who already understands Evernote, is very easy and accessible [4].

I got in touch with some Evernote reps here in Asia just to see how much this Postachio has caught on within the company. While I didn’t get any specific numbers I’m told that APAC general manager Troy Malone is a huge fan, running his own blog on Postachio. Even the Evernote South East Asia blog runs Postachio.

My colleagues here at The Bridge frequently share notes published to the web with Evernote. This interests me, since I myself tend to use Dropbox for that, and I wonder how many other Japanese users also prefer Evernote for web publishing. Perhaps I’m reading too much into a very small difference, but I think this sort of preference could bode well for Postachio.

To learn more about Postachio, check out their video demo below.

  1. Or at least, no reason to pay for a server.  ↩

  2. Or more specifically, Docomo Capital.  ↩

  3. The other co-founder (and coder) is Gavin Vickery, and the third member is programmer Brandon Brown.  ↩

  4. As for my own preference, I’m planning to switch over my personal site to Pelican from Drupal pretty soon. I’d happily use something like Postachio, but because I’m studying Python, I’m going to opt for Pelican. I should also take this opportunity to express how much I really despise WordPress. It started out well, but when the WYSIWYG started randomly injected span and div tags into my code, I decided I had had enough. We still use WordPress on this blog, but for me, it’s not without frequent curse words.  ↩