Your stack

Merlean for your stack

Merlean is framework-agnostic by design: it learns an application from its source, not from a fixed adapter. These pages cover what that looks like in each of the stacks we see most often.

There is no per-framework integration to install and no SDK to wire through your controllers. Merlean connects to your repository, analyses how the application actually works, and executes through the same HTTP interface your own frontend uses. The pages below describe the specifics - what Merlean reads, how authentication is handled, and what tends to need attention in each ecosystem.

Two things decide how cleanly an application analyses, and neither is the framework. The first is whether validation is declared or inlined: a form request, a serializer, a DTO or a schema states the contract precisely, while rules scattered through a controller have to be inferred. The second is whether the backend is connected at all. A frontend describes what the interface offers; only the backend describes what the system permits.

If your stack is not listed, that is not a limitation. Analysis works from source rather than from a per-framework adapter, so an unusual or in-house framework is a question about reading the code, not about whether an integration exists.

See it against your own application

Merlean reads your repository and shows you what it understood before anything is exposed to a user.

Get in touch Read the docs