Plugins

Bring the stack you already run.

Every line Genara writes comes from a plugin — framework, persistence, validation, CI, deployment. Switch them on per project or per service, pin the version, and the generated code follows. Missing something? Write your own plugin in a few lines, or describe it and let the assistant draft it.

8 of 8 switched on · try the toggles

NestJS Servicev1.3.0 · frameworkA NestJS service per spec service: controller, service, guard, DTOs and module.
Prismav1.3.0 · persistenceschema.prisma from the spec, PrismaService wiring and migrate scripts.
Zodv1.4.0 · validationEach data type as a zod schema plus its inferred type.
Swagger / OpenAPIv1.2.0 · APIOpenAPI document generation and the Swagger UI for every service.
Auth Guardv1.2.0 · securityGuards and endpoint decorators derived from your access rules.
Zero-Trust Network Policiesv1.2.0 · securityCilium network policies from who-may-call-whom.
Helm Chartv1.2.0 · deploymentThe deployment chart — workloads, identity, secrets wiring, routes.
GitLab CIv1.2.0 · infrastructureRoot pipeline plus per-service test pipelines other plugins extend.

+ 14 more in the marketplace — Pydantic, Valibot, ArgoCD, OpenBao, Observability, ESLint …

import { definePlugin } from "plugin-sdk";

// Runs once per service the plugin is scoped to.
export default definePlugin({
  async apply(ctx) {
    const name = ctx.specData.services[ctx.serviceId].name;

    await ctx.workspace.mergeJson(
      `services/${name}/package.json`,
      { dependencies: { zod: "^4.4.3" } },
    );
  },
});

Ship backends, not boilerplate.

Genara isn't for sale just yet. Follow us and you'll be the first to know the day we launch.

Get Genara Follow Genara on LinkedIn

import { definePlugin } from "plugin-sdk"; // Runs once per service the plugin is scoped to. export default definePlugin({ async apply(ctx) { const name = ctx.specData.services[ctx.serviceId].name; await ctx.workspace.mergeJson( `services/${name}/package.json`, { dependencies: { zod: "^4.4.3" } }, ); }, });