Case study · selfstoragehosting.com

How we built Self Storage Hosting

Self Storage Hosting is the cloud access control and facility website service Kingpost Software builds and runs itself. Why an office PC is a weak link in a storage gate, and the decisions that shaped the service and the site that sells it.

Self Storage Hosting's home page: a teal header over the headline “Improve operational efficiency and stay serverless”, a Get started button, and a cloud-and-padlock illustration.
selfstoragehosting.com

The problem

In some gate setups the link between the facility management software and the gate runs through one desktop computer in the office. Storable's guide to Storable Easy's gate sync says that computer has to stay on around the clock, with a Windows service checking for changes every five minutes, and the DigiGate manual has the controller programmed from an office PC over a serial cable.

Whatever happens to a desktop then happens to the gate. A disk fails, a Windows update restarts it overnight, someone switches it off at the end of the day, reaching it from home takes a VPN or port forwarding, and in time its operating system runs out of support. Fixing any of that usually means a trip to the site.

Some of the hardware is past its maker’s support as well: PTI Security Systems lists DigiGate, FalconXT and the StorLogix Cloud Adaptor among products it no longer sells or supports. The operators this is for run one facility or a handful, with no IT department to absorb any of it.

Build decisions

Replace the office PC, not the gate

The service takes over the one job the desktop was doing. Changes from the management software land in a cloud service that keeps every facility’s access rules, and a small device on site relays them to the controllers. Working with the hardware already installed comes first; where that is not possible, the answer is a plain account of what replacing it would involve.

Say what happens offline once, in approved words

What a site does when its connection drops is the first thing an operator asks about a cloud gate. The answer is one constant, worded by the owner and rendered unchanged wherever it appears, and the content-policy test fails if it is paraphrased anywhere else. It is never a page’s opening line either: it reassures, it does not sell.

One list behind every repeated claim

The hardware categories and the management-software bridges each appear on more than one page, and each is rendered from a single list, so a correction made once reaches every page. The bridges on offer run from Storable Edge and Storable Easy to INSOMNIAC CIA and to DigiGate, and they are worded as what can be built for a facility, not as listed integrations, until each vendor’s terms have been checked.

No number that cannot be checked

The About page once carried a stats band: a site count, an uptime percentage and a latency figure. They were placeholders, so they were removed, and the content policy now rejects them, along with any security claim beyond TLS, until one can be substantiated. There are no customer logos, testimonials or public prices; pricing is quoted per facility.

Guides that cite the vendors themselves

The resources hub answers what operators actually search for: FalconXT end of life, replacing DigiGate, a gate that stops syncing, which gate systems each management platform lists, and whether a Windows PC is still needed after Windows 10 end of support. Each vendor fact is cited to that vendor’s own documentation, and each guide is dated.

Structured data that claims no more than the page

All JSON-LD goes through one module that refuses SoftwareApplication, Product, review and rating markup. There are no ratings or published prices to support them, and markup that promises more than the page shows is the kind of claim the site was built to avoid.

Where it stands

Self Storage Hosting is live at selfstoragehosting.com, built and maintained by Kingpost Software LLC. The site is a Next.js application served from Netlify behind Cloudflare, and access control and facility websites are sold separately, so an operator can start with either.

Each facility website runs on the operator’s own domain, so the links it earns build up under their name rather than a directory’s. There is no published customer story yet; the site’s own case-studies page says as much, and this page will add one when there is a real one to tell.

Taking a fragile desktop dependency out of a working system without replacing the system around it is the same shape as the legacy rescue and integration work the studio takes on for clients.

  • TypeScript
  • Next.js
  • React