Command Publishing is an independent software publisher in London. We build browser-based applications end to end — the interface, the database behind it and the machines it runs on — and we operate everything we publish.
We fund development by publishing software people actually use. The team that writes it also deploys it, supports it and gets the call when it breaks.
Seven applications in one window: writing, spreadsheets, presentations, a database, desktop publishing, drawing and a diary. Documents open in movable windows inside a single browser tab, so there is nothing to install and nothing to license per seat.
It reads and writes the file formats people already have, installs onto phones and tablets as an app, and carries on working when the connection drops.
Upload a photo, pick your ammunition, and throw it at the faces in the picture. Detection happens on the visitor's own device rather than on our servers, which keeps it quick and keeps photographs off the wire unless someone chooses to share one.
Nothing a visitor submits appears publicly until a moderator has looked at it. Players and pictures both carry rankings, which is what brings people back.
Three kinds of work, all done by the same people. Nothing gets handed over a wall, and there is no queue between a problem being reported and somebody who can fix it.
Complete web applications rather than front ends: accounts, admin tools, file handling, reporting and the database schema underneath. PHP with MySQL, or Classic ASP with SQL Server, depending on where the thing has to live.
Plenty of businesses run on software written years ago that still does its job. We extend it, secure it, make it work on phones and move it onto current hosting — without turning every small improvement into a rewrite.
We operate our own IIS and Linux servers, so backups, patching and uptime are our responsibility rather than a third party's. Production is not somebody else's problem.
We use technology that suits the product and the environment it has to live in, rather than forcing every project through the same framework. Short dependency lists, understandable systems, and code we can still read in five years.
That approach is why our oldest applications are still running, still maintained and still being extended.
Tell us what you are trying to make, fix or migrate, and we will tell you honestly whether it is work we can do well.