Black Morass Services
Core Platform API

The dependable layer between your services and their data

Black Morass Services is a managed platform API that gives deployed Windows and Linux services access to the service database, collects application usage metrics, and validates software licenses — one integration, three essential backends.

Three capabilities, one integration

Every deployment authenticates once and gets scoped access to the full platform.

Database Access

Authenticated endpoints provide structured reads and writes against the service database — configuration, state, and tenant records — scoped per deployment. Responses are versioned so your client software and our platform can evolve on independent schedules, and every query is tenant-isolated by construction, not by convention.

Usage Metrics

A metrics ingestion API accepts application-reported usage events in compact batches and aggregates them into deployment-level statistics for analytics and capacity planning. A few kilobytes per installation per day buys you a live picture of how your entire fleet is actually being used.

License Validation

License status checks return signed entitlement responses with expiration, seat, and grace-period information for compliant software operation. The protocol tolerates disconnected sites: installations operate within a configurable grace window and reconcile automatically once back online.

The deployment lifecycle

Four moments where your software meets the platform.

01

Register

First boot presents the license credential; the platform issues a deployment identity and API tokens.

02

Configure

The service pulls its configuration profile and subscribes to updates — no redeployments for central changes.

03

Operate

Steady-state reads and writes against the service database, plus periodic batched metrics uploads.

04

Renew

Scheduled license re-validation builds a complete audit trail for your compliance team.

Frequently asked questions

The short version of what prospects usually ask.

How does the platform fit into a locked-down corporate network?

All communication is outbound HTTPS on port 443 to a documented set of hostnames. No inbound rules, no exotic ports; a static IP allowlist option exists for strict egress environments.

What happens when an installation goes offline?

Cached configuration keeps it configured, the license grace window keeps it compliant, and metrics queue locally until the API is reachable again.

Which platforms can integrate?

Windows 10/11, Windows Server, and glibc/musl Linux via the client library — or anything that speaks HTTPS/JSON directly against the documented API.

Who can access our data?

Your data is tenant-scoped end to end. Black Morass Services processes it solely to deliver the contracted service, as set out in the Privacy Policy.