Get Started
FAQs
Answers to your most common questions about Amplication usage, management, and implementation
Here are some of the most common questions we receive about Amplication. If you don’t find the answer you’re looking for, please reach out to us on Discord or contact our team directly.
What's the difference between Blueprints and Plugins?
What's the difference between Blueprints and Plugins?
Blueprints are like architectural drawings that define what you want to build - they specify the type of resource, its properties, and relationships with other blueprints. Think of them as basic models that standardize what you build across your organization.Plugins, on the other hand, contain the actual code that determines how those specifications are implemented. They handle the concrete details like code generation, infrastructure setup, and deployment processes. You need both: Blueprints for standardization and Plugins for implementation.
Learn more about implementing custom solutions in our Private Plugins guide.
When should I use custom Blueprints vs. Amplication's standard Blueprints?
When should I use custom Blueprints vs. Amplication's standard Blueprints?
Amplication offers their own standards through Node.js and .NET. They are ideal if you quickly want to adopt industry best practices and leverage Amplication’s public plugin ecosystem. They offer faster onboarding and immediate access to proven patterns.Custom Blueprints are better when you have specific organizational requirements, technology mandates, or unique compliance needs. They offer you complete control of your service architecture but require more initial setup.
They ensure you can generate the code based on your organization’s own standards and requirements.
Explore Blueprint creation in our Blueprint Development guide.
What happens to existing resources when I update a Blueprint?
What happens to existing resources when I update a Blueprint?
Blueprint updates are not automatically propagated to existing resources - this is intentional to prevent unexpected disruptions. After you update a Blueprint (e.g. add a property, or a relation), you’ll need to manually set the values for these changes per each resource.The update process involves reviewing changes, updating configurations, and regenerating code, which creates Pull Requests for your review.
Learn more about how Amplication manages code generation and Git repos in our Smart Git Sync guide.
How are resources impacted when Plugins are updated?
How are resources impacted when Plugins are updated?
When you publish a new Plugin version, Amplication automatically triggers Technical Debt alerts for all affected resources. These alerts appear in the Technical Debt tab for each resource, showing exactly what changes the new Plugin version introduces.Users can review changes through a diff view and choose when to apply the updates. The process generates Pull Requests that can be reviewed and merged according to your team’s workflow.
Learn more about publishing plugins in our Plugin Publishing guide.
How can I see which resources depend on a specific Blueprint?
How can I see which resources depend on a specific Blueprint?
For Blueprints, you can use the “View Resources” feature in the Blueprints section to see all resources created from a specific Blueprint. This filters the Workspace Catalog to show only relevant resources.
How do I get notified about Blueprint or Plugin updates affecting my resources?
How do I get notified about Blueprint or Plugin updates affecting my resources?
Plugin updates trigger automatic Technical Debt alerts visible through in-app notifications and the Technical Debt tab for affected resources. These notifications are targeted to relevant team members and provide direct access to review and apply updates.
Learn more about managing notifications in our Ownership & Visibility guide.