Software Alternatives & Startups

@imqueue VS Lunr EDMS

Compare @imqueue VS Lunr EDMS and see what are their differences

@imqueue

RPC over an inter-communication messaging queue for service-oriented Node & TypeScript back-ends. Self-describing services generate their own clients — no boilerplate, no service discovery, no load balancer.

Rating
0 reviews
Lunr EDMS

Cloud engineering document control and common data environment for owners of long lived assets. Every drawing under revision control, OCR search inside scanned sheets, and DWG, BIM, and point cloud viewing in the browser without a CAD licence.

Rating
0 reviews
Pricing
Paid AU$20,000 / Annually (Lunr Core, single site licence)
Note: These products don't have any matching categories. If you think this is a mistake, please edit the details of one of the products and suggest appropriate categories.

Which is more popular?

Realtime Backend / API popularity
100% vs 0%
alternatives listed
2 vs 9

Base details

Website, pricing, platforms and company facts side by side.

@imqueue
Lunr EDMS
Website imqueue.org lunr.app
Pricing —
Paid AU$20,000 / Annually (Lunr Core, single site licence) Official pricing
Platforms —
Web iOS Android Mac Windows +2
Company — Startup from Australia
Listed in

About @imqueue and Lunr EDMS

In their own words, as submitted to SaaSHub.

@imqueue
Lunr EDMS

No description of @imqueue yet.

Lunr is an engineering document management system and common data environment for organisations that own long lived physical assets. Universities, utilities, water authorities, mines, ports, and government departments use it as the single register for every drawing, model, and manual they hold....

Read more about Lunr EDMS

Features and specs

What each product offers, as listed by its team.

@imqueue 5 features
Lunr EDMS 3 features
  • TypeScript-first design
    imqueue is built with TypeScript at its core, providing strong typing, better IDE support, and compile-time error checking, which helps catch bugs early and improves the developer experience when building microservices.
  • RPC-style messaging abstraction
    It simplifies inter-service communication by abstracting away the complexities of message queue protocols, allowing developers to make calls that feel like local function calls while the underlying complexity of message passing is handled by the framework.
  • Built on RabbitMQ
    By leveraging RabbitMQ as its message broker, imqueue benefits from a mature, battle-tested messaging system with reliable delivery guarantees, clustering support, and a large ecosystem of tools and documentation.
  • Code generation and tooling
    imqueue provides CLI tools and code generation capabilities that can automatically create service clients and boilerplate code, reducing repetitive work and helping maintain consistency across microservices.
  • Microservices-focused architecture
    The framework is specifically designed for building distributed microservices systems, offering features like service discovery and structured communication patterns that address common challenges in distributed system design.

Possible disadvantages

  • Smaller community and ecosystem
    Compared to more mainstream microservices frameworks, imqueue has a relatively small user base and community, which can mean fewer third-party resources, tutorials, Stack Overflow answers, and community-contributed plugins or extensions.
  • Limited documentation depth
    While basic documentation exists, some users report that advanced use cases, edge cases, and troubleshooting guides are not as thoroughly documented as more established frameworks, requiring more trial-and-error or direct code inspection.
  • RabbitMQ dependency lock-in
    Being tightly coupled to RabbitMQ means teams must adopt and manage this specific message broker, which could be a limitation for organizations that prefer or already use alternative messaging systems like Kafka, NATS, or AWS SQS.
  • Learning curve for framework-specific patterns
    Developers need to learn imqueue's specific conventions, decorators, and architectural patterns, which adds an additional learning curve on top of understanding TypeScript and general microservices concepts.
  • Potential scalability concerns for very large systems
    As with many queue-based RPC frameworks, extremely high-throughput or very large-scale distributed systems may encounter performance bottlenecks or require significant additional configuration and tuning of the underlying RabbitMQ infrastructure.
  • Revision control
    Controlled documents with approvals, revision history, automated numbering, and a full audit log
  • XRAY full text search
    OCR and AI across every stored file, including scanned archives, so text inside a drawing is searchable
  • Browser viewers
    DWG, DGN, RVT, PDF, Office, images, BIM models, and point clouds with markup and measurement, no CAD licence

Category popularity

How often each product is chosen within a category, 0–100% relative to the other.

Score bands 0–20 21–40 41–50 51–60 61–100
@imqueue
Lunr EDMS
100% 100%
0% 0%
0% 0%
100% 100%
100% 100%
0% 0%
0% 0%
100% 100%

Questions & Answers

As answered by people managing @imqueue and Lunr EDMS.

What makes your product unique?

Lunr EDMS's answer:

Most document systems read the filename. Lunr reads the drawing.

XRAY runs OCR and AI across everything stored, scanned archives included, so an isolation valve tag inside a 1994 scan turns up as fast as a file saved this morning. Deep XRAY re-reads dense sheets in high resolution tiles, from 2x2 up to 4x4, when the text is faint or crowded.

The second difference is lifespan. Most tools in this space are built around a project and are switched off at practical completion. Lunr is built for the owner, so one system carries the record from project delivery through the decades the asset is actually operated.

Why should a person choose your product over its competitors?

Lunr EDMS's answer:

Three reasons, depending on what you are replacing.

If you are replacing a network drive or SharePoint, you get actual document control: approvals, revision history, automated document and version numbering, and a full audit log on every controlled document, rather than a folder you have to police.

If you are replacing a legacy EDMS, you get a system your own team can run. Changing a workflow does not require a consultant, and keeping it running does not require a specialist.

If you are comparing against project tools, the difference is the timeframe. Those are built to be switched off at handover. Lunr keeps the record for the decades you operate the asset, and checks the handover against the transmittal manifest so the as constructed set that never arrived is caught at acceptance rather than years later in an audit.

Across all three, drawings open in a browser with markup and measurement and no CAD licence, so the people who only need to look are not a licensing cost.

How would you describe the primary audience of your product?

Lunr EDMS's answer:

Asset owners rather than builders. Organisations that hold tens of thousands of drawings across decades of buildings, plant, and infrastructure, and that will still own them in twenty years.

In practice that means universities, utilities and water authorities, mines and metals operations, ports and infrastructure, energy, life sciences, and government departments, mostly in Australia and New Zealand, with hosting also available in the United States.

Inside those organisations the day to day users are document controllers, engineering and asset managers, facilities and campus estate teams, and the contractors and consultants they bring onto projects as external collaborators.

Who are some of the biggest customers of your product?

Lunr EDMS's answer:

  • University of Canberra

User comments

Share your experience with using @imqueue and Lunr EDMS. For example, how are they different and which one is better?

Log in or Post with

Alternatives to @imqueue and Lunr EDMS

When comparing @imqueue and Lunr EDMS, you can also consider the following products.