Analog is the fullstack meta-framework for building applications and websites with Angular, powered by Vite for development and build and by Nitro for server and deployment integrations, and it is aimed at Angular developers and teams who want the file-based routing, server routes, and hybrid rendering that frameworks such as Next.js and Nuxt provide in other ecosystems.
What it is
Analog is the meta-framework for building applications and websites with Angular. It layers conventions that Angular itself does not ship — file-based routing, integrated server and API routes, server-side data fetching, and hybrid rendering — on top of the Angular framework, so one project can serve rendered pages, static output, and backend endpoints instead of a client-only single-page application. The build and development pipeline is powered by Vite, and the repository topics confirm the scope: angular, framework, fullstack, meta-framework, nitro, router, server-side-rendering, ssr, ssg, static-site-generator, vite, web.
The concrete problem it solves is the gap between plain Angular and the batteries-included meta-frameworks available elsewhere. A plain Angular application has no opinion about routing conventions, no first-class server runtime, and no markdown-to-route path, so teams assemble those pieces themselves or adopt a framework from a different ecosystem. Analog replaces that assembly work with a single Angular-native toolchain, in the same way Next.js, Nuxt, SvelteKit, and Qwik City serve their own ecosystems.
Key capabilities
- File-based routing driven by the filesystem, listed in the README as a first-class feature.
- Integrated API and server routes, so backend endpoints live in the same project as the Angular application.
- Hybrid SSR and SSG support, allowing a deployment to mix server-rendered and statically generated output.
- Static-site-generator and server-side-rendering use cases, reflected directly in the repository topics.
- Server and deployment integrations powered by Nitro, which supplies the server runtime and deployment targets.
- Markdown as content routes, giving a supported path for content-oriented sites such as blogs and personal sites.
- Builds through Vite via
@analogjs/vite-plugin-angular, published to the Vite plugin registry, with support for Vitest and Storybook and for both Angular CLI and Nx workspaces.
Who uses it and how
- Angular teams that want the meta-framework workflow — routing conventions, server routes, rendering modes — without leaving Angular for Next.js, Nuxt, SvelteKit, or Qwik City.
- Content and publishing projects, matching the registry category, where markdown as content routes and hybrid SSG output suit blogs and personal sites.
- Applications needing server-side data fetching alongside client rendering, deployed through Nitro's server and deployment integrations.
- Teams working in Angular CLI or Nx workspaces, since both are explicitly supported.
- Projects that want Vite-based builds with Vitest and Storybook testing in one toolchain, with a community of 140 contributors reachable through the Analog Discord.
Getting started
Scaffold a project with the package manager of choice — npm create analog@latest, pnpm create analog@latest, bun create analog@latest, or yarn create analog — then follow the prompts and start the development server. Documentation and an Open in StackBlitz link live at https://analogjs.org.
How it compares
The README positions Analog against Next.js, Nuxt, SvelteKit, and Qwik City as the Angular counterpart, the same class of tool with a similar experience, built on Angular rather than React, Vue, Svelte, or Qwik. Where those frameworks target their own rendering libraries, Analog is the option for a codebase already committed to Angular. It is MIT licensed, and the facts list no paid tier, hosted product, or commercial offering that it replaces.
When to use it — and when not to
Choose Analog when the project is Angular and the team wants meta-framework conventions — file-based routing, server routes, hybrid SSR and SSG — from one maintained toolchain rather than assembled in-house. Do not choose it as a general-purpose framework for non-Angular stacks, and expect to own deployment: the server and deployment pieces arrive through Nitro, so a self-hoster selects and operates that runtime rather than inheriting a managed offering. The README is mostly a feature list that defers detail to analogjs.org, and the repository carries 44 open issues, so anyone weighing it should read the documentation and the issue tracker before committing.
