Bridge your cloud apps to the office floor.

DSX lets any cloud web app talk to on-premise hardware — silent printers, network drives, scanners, scales, even legacy ODBC databases — without exposing your office network. Outbound-only, multi-tenant, and designed for the bespoke apps that can't fully retire on-prem dependencies.

DSX enquiry See how it works

The "last mile" problem.

Your business has moved most operations to the cloud — but a few critical workflows still need to talk to physical things in the office. The label printer behind the warehouse desk. The shared drive that feeds the production line. The barcode scanner at goods-in. The legacy database the accounts package depends on.

Most cloud apps handle this badly — either they pretend it isn't a problem (and force the user through a browser print dialog every time), or they require you to open firewall holes and run servers in your DMZ. DSX is built for this last mile, and nothing else.

How DSX works.

Two components — a cloud Hub and a small on-prem Client — connected by an outbound-only secure channel. Your bespoke app talks to the Hub via a simple REST API and never has to know the Client exists.

Component 1

DSX Hub

A multi-tenant cloud service. Your bespoke apps integrate via a simple REST API. On-prem Clients connect to it over a secure channel.

→ Hosted and managed by Digital Spark
→ Signed-payload command envelope
→ Per-tenant isolation throughout
→ Secure file broker with one-time URLs
→ Three-layer authentication

Component 2

DSX Client

A small Windows agent that runs on a single office machine. Connects outbound to the Hub. Receives signed instructions. Executes them against local hardware or drives. Self-updates without IT involvement.

→ Outbound-only — no inbound firewall rules
→ Runs as background Service or system tray app
→ OS-level credential protection
→ Self-updating — no IT ticket needed
→ One install supports many cloud apps and tenants

Architectural choice: no firewall holes, ever.

The Client initiates the connection to the Hub — not the other way around. That means no inbound firewall rules, no NAT pain, no per-machine certificate management. Your IT team approves an outbound HTTPS connection (already allowed for browsing) and it just works.

Common uses.

DSX shines wherever a cloud app needs to reliably interact with something physical or local on the office floor. Two patterns cover the bulk of SME bespoke-app needs:

Pattern 1

Silent print

Your cloud app sends a PDF and a printer name. The Client prints it with no browser dialog, no user prompt. Dispatch labels, picking lists, certificates, invoices — straight from the cloud to the right printer, every time.

Pattern 2

Secure local file-write

Your cloud app sends a file and a target path. The Client writes it to a pre-approved drive location under hard path-security guardrails. Reports to the shared drive, exports to the line system, attachments into a managed folder.

Advanced use cases.

DSX is designed around a generic device-handler abstraction, so adding new device types is additive — not a rewrite. The capabilities below are either in production today, in flight, or on the customer-driven roadmap:

Barcode scanners Weighing scales Legacy ODBC / OLEDB bridge PLCs & sensors Webhook callbacks Customer self-hosted Hub Tenant self-onboarding More — driven by customer ask

Built for bespoke apps. Sold to their builders.

DSX isn't a consumer product — it's an infrastructure component for the teams (us, you, anyone) building bespoke cloud apps for SMEs. It's the answer to "the customer needs this to print silently / talk to a scanner / write to their shared drive" without committing to a six-month custom integration each time.

For Acçodus™ migrations

When an Access app being modernised has print or local-drive dependencies it can't lose, DSX is the clean answer.

For Forge engagements

Any bespoke web app we build that needs the office floor can integrate DSX via the SDK — typically half a day of work.

For third-party developers

Building a SaaS that needs the same capability? DSX is multi-tenant — your customers are your tenants, your billing is your business.

Pricing.

DSX is a SaaS — sold as a monthly per-tenant service. Two components: a fixed minimum service fee covering the hosted Hub and a slot for your Client, plus a metered allowance of data processed per month.

Component A

Minimum monthly service fee

Covers your tenant on the hosted Hub, your Client install, secure transit, support, and a defined allowance of data processed per month (KB throughput).

Component B

Metered data over allowance

If your usage exceeds the included monthly allowance, additional throughput is billed per KB. Visible from your dashboard, no surprises.

Final pricing levels are being finalised against pilot usage data — Founders customers will be quoted before launch and locked in at preferential rates.

Building something that needs DSX?

Tell us what your bespoke app needs to do on the office floor — we'll work out whether DSX fits and what integration looks like.

DSX Enquiry