Yarosoft
Our work

Real systems, running real businesses.

We keep clients' names private unless they've told us otherwise. What we don't hide is the work: each case study ends with the technical detail, written so you can hand it to your IT team.

Client case studies

Hosting control plane, simplified A control plane holds how every site should be set up. Agents on each web server reach out to it, report what they see and run recorded jobs. Each site runs on a home server with a standby copy on a second server. Backups go to a local tier and an off-site tier. Control plane Inventory · desired state Jobs, audit trail, alerts agents reach out only Web server A Home for some sites Standby for the others Each site walled off Web server B Home for some sites Standby for the others Each site walled off standby sync Local backups (encrypted) Off-site backups (encrypted)
Web hostingLive

400 infected websites, rescued and rebuilt

A rescue across the whole estate, then a control plane that knows every site, walls each one off and keeps a standby copy ready.

View case study
Operations platform, simplified An agent on every Linux and Windows server pulls signed settings from the operations panel and never takes commands. Agents send encrypted backups off-site and report checks to the panel, which alerts staff by email and SMS. Operations panel Checks · jobs · roles Alerts by email and SMS pull signed settings, report results Linux servers Agent Web, data, legacy Windows Agent Core business system File exchange Agent Order flow Off-site storage · encrypted before it leaves each server
National retailLive

Nothing had gone wrong in years. That was the problem.

No backups running and rising cyber risk. Now every server, Linux and Windows, is watched, backed up and proven to recover.

View case study
Compliance platform, simplified Several client firms use one platform. Each firm's records are walled off inside the database. Complaints and incidents registers carry regulatory deadlines. Before any AI call, personal details are masked locally and only Australian-region AI providers are used. Client firm A Client firm B Client firm C One platform Complaints and incidents registers Regulatory deadlines built in · sign-in with two-factor Firm A's records Firm B's records Firm C's records Mask personal details On our own servers, first AI pre-fill Australian-region providers only
Financial-services complianceRolling out

Regulator deadlines kept by the system, not by memory

Many firms on one platform, each walled off, with deadlines built in and AI that only sees masked records.

View case study
Trading platform, simplified Data collectors feed a shared host that runs algorithms as plug-in packages. A compute fleet trains and replays models. Every order passes risk checks before execution through broker connections or a Windows bridge. Results publish to a client dashboard with subscriptions and notifications. Data collectors Market and research data Compute fleet Training and replay Shared host Algorithm plug-ins Isolated state per algorithm Risk checks Broker connections and our Windows MT5 bridge Client dashboard Subscriptions, notifications
Trading platformEngineering only

Software where every decision is checked before it acts

Data collection, a compute fleet, risk checks and execution across several channels, working as one.

View case study

Diagrams are simplified, drawn from the published project details. They are not screenshots.

More from our experience

The case studies are only part of it

Behind Yarosoft are two decades of turning businesses that ran on effort into businesses that run on systems. Two examples:

Ecommerce

From processing orders to selling

An online business ran its orders from spreadsheets and fulfilled them by hand, so growth only meant more processing. We replaced it with a fully automated fulfilment pipeline, and the business's attention moved from keeping up with operations to growing sales.

Ecommerce logistics

A 3PL bill cut by 33%

While building an integration with another online business's third-party logistics (3PL) warehouse, we noticed it was paying for far more storage than it needed. We wrote a storage optimisation algorithm that reduced its allocation, and its monthly bill dropped by 33%.

Tell us what's slowing you down.

Describe how things run today, or what worries you. We'll come back with a plain-English view: what we see, what we'd fix first, and roughly what it would involve. It's free, and yours to keep.

Get a free review