Skip to content
Lia
Industries

The archive is the asset. Most of it is unreachable.

iLeaf builds content and publishing platforms, including BMJ's digital transformation, an interactive e-book application bridging physical and digital reading, and social publishing products. The recurring problem is not producing more content but making a large existing archive findable, licensable and useful — which is now as much a retrieval problem as a publishing one.

Talk to a solutions lead See client results
Ask Lia about media & publishing

What this includes

Editorial & content platforms
Large-scale systems for producing, reviewing and publishing, including clinical evidence platforms.
Interactive digital publications
E-book and rich-media applications connecting printed works to digital editions.
Archive retrieval
Semantic and graph-based search across decades of back catalogue that keyword search never surfaced.
Subscription & entitlement
Who may read what, across institutions, seats and licence terms, without blocking legitimate readers.
Social & community products
Publishing applications with the interaction layer — following, commenting and sharing — built in.
Content licensing for AI
Preparing an archive to be licensed and queried as a product rather than scraped as a cost.

How we run it

Every phase ships something usable on its own, so you are never holding a half-finished system waiting on the next milestone.

  1. Treat the back catalogue as inventory

    Most publishers monetise the recent and neglect the deep archive, which is usually the larger asset and the cheaper one to unlock.

  2. Protect editorial authority

    Generated summaries are labelled and traceable to the source. A publisher's credibility is the product, and it is not worth an efficiency.

  3. Entitlement without friction

    Access control that fails closed on a paying institution costs more than the leakage it prevented.

  4. Migrate without breaking links

    Citations and inbound links are accumulated authority. A replatform that breaks them discards years of it.

What we build it with

  • React
  • Next.js
  • Node.js
  • PostgreSQL
  • Elasticsearch
  • Graph RAG
  • Vector search
  • Swift
  • Kotlin
  • CDN / caching
  • SSO / entitlement
  • AWS

Questions we get asked

What publishing experience does iLeaf have?

The largest engagement is BMJ's digital transformation, a clinical evidence and content platform. Alongside it sit an interactive e-book application bridging physical and digital books, and social publishing products with community and sharing features built in.

Can you make our archive searchable by AI?

That is one of the most common requests now. It combines semantic and graph-based retrieval over the back catalogue with entitlement checks, so answers stay inside what a reader is licensed for, and every generated summary remains traceable to the source article rather than floating free of it.

Will a replatform cost us our search rankings?

Not if link continuity is treated as a requirement rather than a cleanup task. Citations and inbound links are accumulated authority, so URL mapping and redirects are planned before migration and verified after — a publisher that breaks its own citations discards years of standing.

Related

Let’s talk about media & publishing.

Tell us what you are running and what it needs to do next. We will tell you honestly whether we are the right team for it.

Talk to a solutions lead
Selected work

Media & Publishing: the work behind this