Digital rights management and secured fulfilment, from DMI Systems hello@dmi.systems Operator login
Digital Media ReserveAn imprint of DMI Systems

Rights-protected fulfilment since 2007

Digital Media ReserveDRM protection and secured fulfilment for your eBooks, documents and video

Adobe handed the eBook platform to Wipro in July 2025. Adobe ID sign-in for Adobe Digital Editions ends 23 June 2026. If you fulfil protected books, this affects your readers.

Secure your digital publications, share online with confidence!

Digital Media Reserve is a centralised repository for your digital publications and a fulfilment system for rights-protected files. Publishers and retailers upload to the reserve, integrate through our web services, and sell or lend from their own storefront — with the encryption, the licence and the download link handled on our side.

#IP#DRM#DLT
Protect the IP
A publishing workflow seamlessly joined to a robust, scalable digital studio — so rights travel with the file, not with a spreadsheet.
Manage the rights
A flexible implementation of the best-of-breed rights management stack, now continued as ByteBooks Content Server under Wipro.
Trace the chain
We are designing a distributed-ledger publishing chain to make rights and royalty movement auditable end to end.

What we protect

Two reserves, one gateway

Documents and video are broken in completely different ways, so they need completely different locks. DMR runs both behind one account, one integration and one invoice.

And two levels, not one

Full DRM where the title earns it; social DRM — the buyer's identity watermarked into an unencrypted file — for free chapters, review copies and low-risk backlist. Set per title, not per account. Compare the two →

How it works

Four steps from master file to monitored sale

The same four whether you are selling one title from a WordPress page or fulfilling a 4,000-title list to three retailers.

  1. Upload

    Your masters go into the reserve once — EPUB, PDF/A, video — with their metadata, versioned and held for good.

  2. Choose protection

    Full DRM or social watermarking, per title. Set the loan period, the copy model and the permissions that go with it.

  3. Sell or lend

    From your own storefront through our API, or from a lending collection. You keep the customer and the money.

  4. Monitor

    Every fulfilment logged by title, format, channel and period — reconcilable against your own sales and your funder's questions.

Who it is for

Digital infrastructure for document security.

Publishers & retailers

Protect your digital publications
Upload once; every fulfilment is encrypted against the buyer, not against the file.
Sell under secured DRM from your own website
Your storefront, your brand, your customer record — our licence server.
Sell to end-users or lend to libraries
Perpetual sale, timed loan and institutional licence from the same catalogue.

Customised retail system

A storefront you do not have to build
Antrik, our retail system, gives you catalogue, cart and checkout already wired to the reserve.
Metadata that behaves
ONIX for Books in, clean product pages out, via OnixMaster — which brings a web-store of its own.
Payment gateway of your choice
We integrate with what you already use; fulfilment happens after your payment confirms.

Institutions

Lend with a return date
Copy models, holds and queues, and content that returns itself on schedule.
Course video that stays in the course
Watermarked, device-bound playback for enrolled students only.
Accessible by default
NIMAS, DAISY and EPUB 3 accessibility work sits in the same group, at NIMAS Master.

Integration

Three calls stand between your checkout and a protected download

Your site keeps the customer, the cart and the money. DMR issues the licence. The retail flow is deliberately small — check the title is available, exchange your transaction for a download link, and re-issue that link whenever the customer needs it again.

New integrations use the REST API. The original SOAP services stay documented and supported for retailers already built on them, and ONIX catalogue sync keeps your product data in step without anyone re-typing it.

Read the integration guide
REST — fulfil a purchase
POST /v1/transactions
Authorization: Bearer <retailer token>

{
  "transaction_id": "your-order-4471",
  "item_id":        "dmr:9788195xxxxxx",
  "format":         "epub",
  "protection":     "acs"
}

200 OK
{
  "download_url": "https://…/fulfil/9f2c…",
  "expires_at":   "2026-09-13T11:04:00Z"
}

Same three operations in SOAP, for retailers already integrated: CheckAvailability, NewTransaction, RegenerateDownloadLink.

Act before 23 June 2026

Adobe Content Server did not go away. It changed hands.

In July 2025 Adobe transferred maintenance, support and the product roadmap for Adobe Content Server and RMSDK to Wipro Engineering — Connected Services. The platform now runs as ByteBooks. Adobe Digital Editions itself is unchanged, but the sign-in behind it is not: from 23 June 2026, Adobe ID stops working and readers need a ByteBooks ID created with the same email address.

For a retailer, that is a support event, not a technical one. Your customers will hit a password-reset error inside an app you did not write, about an account you do not hold, for a book they bought from you.

See the transition checklist

What your support desk will see

RMSDK applications return a new error code, E_ADEPT_RESET_PW_REQUIRED, when a reader signs in with a credential that has not moved to ByteBooks. Handle it explicitly and you turn a ticket into a one-screen instruction.

DMR briefs your support team, supplies the reader-facing wording, and tests the re-authorisation path against your own titles before the cut-off.

Tell us what you publish. We will tell you how it gets protected.

Reserve accounts are opened after a short qualification call — catalogue size, formats, where you sell, and whether video is in scope. Most publishers are uploading within a week.