Relume

What Relume is

Relume helps freelancers and agencies build marketing sites with AI, and its workflow moves from a brief in writing through a sitemap and wireframes and on to pages ready to publish.

The design decision underneath the product is the part to grasp, and the company says it outright: what comes out is assembled, not generated. The system does not write raw code. It selects and arranges components from a library built to a specification.

How the assembling works

Starting from a brief, the platform produces a sitemap and then wireframes, which is the order a competent web project actually follows. Structure before decoration is a discipline that generated sites usually skip, and skipping it is why so many look plausible and read badly.

Export is offered to three destinations, each treated with attention to what that destination needs. Output for Webflow arrives with clean class names following a common convention and needs no tidying, which matters because hand-cleaning a generated export is where the promised time saving usually disappears.

On security, the disclosure is unusually precise about what exists and what does not. Certificates, protection against distributed denial of service and an availability objective are stated, and the audit standard is listed as pending rather than achieved, which is the honest way to put it.

Who it is for

The intended users are studios and freelancers who produce marketing sites again and again, plus teams wanting wireframes to land in a design file, a site builder or a code project without tidying.

It is a poor fit for anybody expecting a finished design. Wireframes are a middle stage, and a business that wants a complete site handed over will still need somebody to supply the visual layer.

Points to weigh

A pending audit standard is not a certification and should never be presented as one. For a buyer that has to satisfy procurement, the practical effect is that no report can be asked for yet, and the sensible course is to treat the standard as work under way rather than an assurance already in place.

Neither the charge nor where the free account stops appears anywhere, so what adoption costs and what the free route covers cannot be worked out. The questions that matter are the charge per seat or per project, how many projects are included, and what becomes of exports when a subscription ends.

Two things to check. Assembling rather than generating is the strongest case for the product, so copy a demo project and examine the result: class names, the variables in the design file, and the components in the code. And because the value sits in the library rather than in a model, the product's durability depends on how well that library is maintained over time.