Native analysis for modern polyglot applications.
Farion analyzes supported languages and frameworks as parts of one application architecture. Routes, services, handlers, dependencies, and data flows remain connected even when the system spans several technology stacks.
Preserve the semantics of each language.
Farion uses dedicated parsers and analyzers for supported languages. Types, symbols, calls, object fields, framework conventions, routes, and handlers remain available to SAST, data-flow analysis, exploitability assessment, and architecture discovery.
Connect services instead of treating repositories as isolated projects.
A frontend, backend, worker, RPC service, and message consumer may use different languages while still forming one product. Farion detects their entry points and service boundaries and represents them in one application model.
Recognize the structures that expose application behavior.
Framework-aware analyzers discover controllers, routes, handlers, public symbols, RPC endpoints, WebSockets, messaging entry points, and other supported application structures.
Supported route and application frameworks
Go
Gin
Fiber
Echo
net/http
Chi
Python
Django
Flask
FastAPI
Tornado
Pyramid
Bottle
Sanic
Quart
Node.js, JavaScript, TypeScript, and frontend
Express
Fastify
Restify
Koa
Hono
Hapi
NestJS
Next.js
Nuxt.js
SvelteKit
Qwik
Fresh
Stencil
tRPC
Remix
Astro
React
Vue
Angular
Solid
Ember
Java
Spring Boot
Servlet
JAX-RS
JAX-WS
JSF
Jakarta MVC
WebSocket
Kotlin and JVM
Ktor
Quarkus
Micronaut
http4k
Vert.x
.NET
ASP.NET Core MVC
Minimal APIs
Blazor
Rust
Axum
Actix Web
C and C++
Analysis without framework-specific route discovery
Cross-cutting entry points
Messaging
Message Handler
Public Symbol
Turn framework detection into an application map.
Farion uses recognized routes, handlers, and service relationships to generate a microservice and application architecture diagram. The same model powers route grouping, data-flow analysis, and exploitability assessment.
Frequently asked questions
No. Framework knowledge contributes to entry-point detection, call-path construction, dependency-injection resolution, data-flow analysis, and finding context.
Yes. Messaging entry points and message handlers can be recognized and connected to findings and data flows.
See how Farion works on your application.
Request a guided evaluation or walk through the relevant workflow with our technical team.