amplication

Generates complete data models, DTOs, and database schemas from visual entity-relationship diagrams (ERD) composed in the web UI. The system parses entity definitions through the Entity Service, converts them to Prisma schema format via the Prisma Schema Parser, and generates TypeScript/C# type definitions and database migrations. The ERD UI (EntitiesERD.tsx) uses graph layout algorithms to visualize relationships and supports drag-and-drop entity creation with automatic relation edge rendering.

Generates complete, production-ready microservices (NestJS, Node.js, .NET/C#) from service definitions and entity models using the Data Service Generator. The system applies customizable code templates (stored in data-service-generator-catalog) that embed organizational best practices, generating CRUD endpoints, authentication middleware, validation logic, and API documentation. The generation pipeline is orchestrated through the Build Manager, which coordinates template selection, code synthesis, and artifact packaging for multiple target languages.

Manages service versioning and release workflows, tracking changes across service versions and enabling rollback to previous versions. The system maintains version history in Git, generates release notes from commit messages, and supports semantic versioning (major.minor.patch). Teams can tag releases, create release branches, and manage version-specific configurations without manually editing version numbers across multiple files.

Generates database migration files from entity definition changes, tracking schema evolution over time. The system detects changes to entities (new fields, type changes, relationship modifications) and generates Prisma migration files or SQL migration scripts. Migrations are versioned, can be previewed before execution, and include rollback logic. The system integrates with the Git workflow, committing migrations alongside generated code.

Provides intelligent code completion and refactoring suggestions within the Amplication UI based on the current service definition and generated code patterns. The system analyzes the codebase structure, understands entity relationships, and suggests completions for entity fields, endpoint implementations, and configuration options. Refactoring suggestions identify common patterns (unused fields, missing validations) and propose fixes that align with organizational standards.

Manages bidirectional synchronization between Amplication's internal data model and Git repositories through the Git Integration system and ee/packages/git-sync-manager. Changes made in the Amplication UI are committed to Git with automatic diff detection (diff.service.ts), while external Git changes can be pulled back into Amplication. The system maintains a commit history, supports branching workflows, and enables teams to use standard Git workflows (pull requests, code review) alongside Amplication's visual interface.

Manages multi-tenant workspaces where teams collaborate on service definitions with granular role-based access control (RBAC). The Workspace Management system (amplication-client) enforces permissions at the resource level (entities, services, plugins), allowing organizations to control who can view, edit, or deploy services. The GraphQL API enforces authorization checks through middleware, and the system supports inviting team members with specific roles and managing their access across multiple workspaces.

Provides a plugin architecture (amplication-plugin-api) that allows developers to extend the code generation pipeline with custom logic without modifying core Amplication code. Plugins hook into the generation lifecycle (before/after entity generation, before/after service generation) and can modify generated code, add new files, or inject custom logic. The plugin system uses a standardized interface exposed through the Plugin API service, and plugins are packaged as Docker containers for isolation and versioning.

Automatically manages package updates and patches for generated services, reducing technical debt and maintaining consistency across the codebase. The system tracks dependencies in generated services, detects outdated packages, and can automatically commit updated package.json/package-lock.json or .csproj files to Git. This capability is integrated with the Build Manager and Git Integration, allowing teams to keep all services synchronized on the same dependency versions without manual intervention.

Generates both GraphQL and REST API endpoints from entity definitions with automatic schema validation and type safety. The system creates GraphQL resolvers, REST controllers, and request/response DTOs with built-in validation decorators (class-validator for NestJS, data annotations for C#). The generated endpoints include OpenAPI/Swagger documentation automatically, and the system validates incoming requests against the generated schemas before passing them to business logic.

Generates authentication and authorization middleware for generated services, supporting JWT tokens, role-based access control (RBAC), and permission checks. The system creates authentication guards (NestJS @UseGuards decorators, C# [Authorize] attributes), permission validators, and token verification logic based on service configuration. The generated middleware integrates with the service's entity definitions to enforce field-level and endpoint-level access control.

Generates production-ready Docker configurations and GitHub Actions CI/CD workflows for generated services. The system creates Dockerfiles optimized for Node.js and .NET applications, docker-compose files for local development, and GitHub Actions workflows that build, test, and deploy services. The generated CI/CD includes automated testing, linting, security scanning, and deployment to container registries or cloud platforms.

Manages service configuration and environment variables for generated services across development, staging, and production environments. The system generates environment configuration files (.env, appsettings.json), configuration classes, and environment-specific overrides. Configuration is managed through the Amplication UI and stored in the service definition, allowing teams to update configuration without code changes and deploy the same service image to multiple environments.