Platform services
The infrastructure underneath: sending email, storing and resizing media, publishing to social networks, signing documents, rendering video, recording cameras. Each is sold on its own and each underpins a product above it.
· 5 min read
Rutba Vision: video surveillance for camera networks past the size one recorder copes with
Rutba Vision spreads recording, AI and search over nodes on each site, joins the sites at a hub without moving their footage, and turns AI on camera by camera. This is how it is built, and why the recorder never stops.
· 3 min read
Forty-six apps from one image: how a release went from 38 minutes of builds to under 12
Every Rutba suite app used to be built and shipped as an image of its own: 46 builds, 38 minutes and 4.1 GB of nearly identical copies. Since 13 October they compile into one image in under twelve minutes and run in 14 containers instead of 46.
· 4 min read
Measuring is not enforcing: a licence check that never stops your work
Every Rutba deployment now tells us what it is running, and gets back what it is licensed to run. Nothing is refused by that answer: drift is recorded, said out loud and billed if somebody chooses, never turned into an outage you did not plan.
· 4 min read
A launch morning waits ten minutes. A looping script is paused
Rutba Relay now counts the deliveries each organization started in the last hour. Just over its ceiling, a publish is told to wait ten minutes. Four times over is not a person, and that organization’s publishing is paused until somebody looks.
· 3 min read
The view our operators get of your Relay workspace shows its shape, not your posts
Running a publishing service means staff sometimes need to look inside a customer’s workspace. What they see is who is in it, what is connected and how recent posts went. Never a credential, and never a word of a post.
· 3 min read
A kill switch with a name on it
When a social network changes something overnight, a publishing service can fire thousands of failing requests at it and collect strikes against your accounts. The Relay’s switches stop that, and every one records who threw it and when it clears.
· 3 min read
One Rutba account opens the Relay, and the Relay no longer keeps passwords of its own
The Relay used to run its own sign-up, passwords, second factor and invitations. Now a person signs in once with their Rutba account, and their organisation gives them the Relay the way it gives them anything else.
· 3 min read
Every signature API returns an audit report the vendor vouches for
Which is worth exactly as much as your relationship with that vendor. Ours returns a record anyone can check independently: from a public endpoint, with no key, that does not reach your systems at all.
· 2 min read
Nobody notices email deliverability until sales drop
Bounces, complaints and the slow drift into spam folders are a reputation problem, and reputation is a property of your domain rather than of any one product. So transactional mail and campaigns go out through the same relay.
· 2 min read
Posting the same thing to six networks by hand is an hour a day nobody has
The scheduling half is well served. The part that is not: a documented API the console itself is built on, so anything else (including an assistant with the same permissions a person has) can publish the same way.
· 2 min read
Storing five versions of every product photo is how thumbnails go stale
It is also how storage bills grow. Keep one master and generate whatever dimensions are asked for at request time, and a redesign that changes every image size costs a URL change rather than a re-upload.
· 3 min read
Your cameras keep recording when the internet does not
Cloud camera services charge monthly to store your footage on someone else’s disk, and stop working the moment the line drops. Rutba Vision runs on a box in your building. The only thing that talks to us is a licence check.
· 3 min read
Marketing creative goes stale the moment a price changes
The ad is not wrong when it is made. It becomes wrong on the Tuesday somebody edits the catalogue, and nothing about the file says so. Rendering one template once per row of a product sheet makes the fix a re-run rather than forty edits.
