I’m Yuval, and for the past several years I’ve been building dev tools (some of you might know Amplication). Over that time, we’ve all seen the rise of AI copilots and agents. They are useful for individuals in the IDE, but limited when it comes to how teams actually ship software. I believe the next step is moving beyond copilots into *autonomous, continuous AI* that runs inside the SDLC itself.
That’s what we’re building with https://overcut.ai/. It connects directly to GitHub, Jira, and other tools, and runs workflows that handle things like:
- Reviewing PRs
- Writing tests
- Generating specs and docs
- Triaging and resolving issues
- Opening and updating PRs automatically
The difference is that instead of manually operated assistants or black box agents, you define the workflows (like CI/CD pipelines, but for AI agents). This makes it transparent and under your control.
We provide several ready-made playbooks, and you can also build your own for anything you can imagine on top of Git and tickets. There are built-in integrations to GitHub, GitLab, Bitbucket, Azure DevOps, and Jira.
Would love to hear your thoughts: what workflows would you want AI to take over, and what would hold you back from trusting something like this?
Prisma’s type-safe database access, powerful query API and migrations were a game-changer for Amplication building our platform and also the code we generate.
Agree with you on that! To my opinion the plugins are the most excising in this version. We are still working on the doc on how to create your own plugins
Hello, Yuval here, founder of Amplication. I’m very excited to share with you what the Amplication team is working on.
Amplication saves engineers from undifferentiated heavy lifting in application development, while helping organizations speed up delivery, and enforcing best practices and standardization across multiple teams and developers.
Amplication accelerates the development of backend applications and microservices with high-quality code generation, streamlining and automating development while solving issues that delay production readiness.
We built Amplication so developers like us could focus on coding the parts that matter rather than get distracted by repetitive tasks and boilerplate code.
Amplication is an open-source platform that lets you easily configure your backend services, by generating a human-readable and editable TypeScript Node.js codebase. The generated code includes everything you need to start writing your business logic.
Amplication continuously generates the code based on changes in the schema and configuration, then pushes the code to a GitHub repository to allow developers to continue off and edit it further based on their needs.
Today's launch of our v1.0 also incorporates a plugin architecture that enables developers to develop their own plugins to implement best practices, code conventions, custom integrations, and virtually anything in the generated code. Developers can use plugins created by Amplication’s core team, by our community, or create their own.
We already have several plugins on our Github plugins repo -https://github.com/amplication/plugins, including support for Kafka, MySQL PostgreSQL, Passport JWT, Passport Basic authentication, and the list is growing.
We can’t wait for you to experience Amplication, please share your thoughts.
Thanks for the feedback.
As for the pricing, this was an initial draft that was published some time ago, and since then, some concepts have been changed. We are working on new pricing tiers, which will be published soon - anyway, the product will be free and open-source for individual developers and open-source projects.
About the users - we are building Amplication for pro backend developers. The code we generate is built based on best practices with well-known technology, so it does not require learning anything unique to Amplication.
Also, we provide several ways to customize the code without breaking the link to Amplication so you can add business logic and customize your server with minimal conflicts.
When you build your server with Amplication, you get the server with all your data models, DTOs, and more so it saves you a lot of writing.
We are working now on a new version that will allow you to build microservices with or without databases, with or without queues and message brokers. And on top of that, we will introduce a plugin system allowing teams to use their own best practices and standards for the generated code.
Would love to get your feedback or any suggestions or ideas you may have.
Amplication | REMOTE (US/EU Time zones) | Full Time | Developer Advocate/DevRel | http://www.amplication.com
About Amplication
Amplication is a developer-first company, building an open-source PaaS for cloud development. Amplication eliminates all the boilerplate, repetitive coding, infrastructure, and other repetitive tasks while keeping developers in full control of their code and apps. We are a small and dedicated team with funding from top-tier global VCs, focused on community and bottom-up adoption.
Stack includes: TypeScript, Node.js, NestJS, Prisma, Docker, K8s, PostgreSQL, REST, GraphQL,
Developer Advocate/ DevRel
As Developer Advocate, you will be required to build awareness and adoption of Amplication, and assist our community members in building their next app with Amplication. This role could be a good fit if you are an experienced developer advocate with high technical and personal skills. You must have the engineering knowledge required to build demos, call APIs, and support other engineers in developing and customizing their apps with Amplication. In addition, you should like giving presentations, creating content, and building relationships with the community. You will be required to organize meetings and events, mentor developers, and write technical blogs and articles.
We try to solve precisely that with Amplication, where we combine low-code with custom code. We generate a node.js and react application based on low-code configuration and push the code to your GitHub repo
Hello, co-founder here: working with small businesses over the years, I saw a lot of them working and managing critical business processes using Excel files that start small but quickly grow out of proportion.
As a developer, the security, scalability, integrity, and durability implications made me feel nervous every single time. On many occasions, I was asked to build a full-scale app to replace the Excel file once it becomes too risky for the business to keep relying on a spreadsheet.
Like with every project, you have to go through several steps to produce a reliable service:
1. Design the data model based on the excel file
2. Building the infrastructure (database, ORM, web framework, packages, libraries, etc)
3. Adding authorization and authentication
4. Making sure everything is written with best practices, security, performance, and maintainability in mind.
That process was tedious and repetitive, even when using an existing boilerplate project.
Recast was designed exactly for these types of projects to save time and money and bring the development process up to speed in no time, eliminating the painful process. We generate a TypeScript Node.js source code that includes a GraphQL and REST API, authorization, authentication, identity management, logging utility, error handler, and a React admin UI - just by importing a data schema from excel.
The generated source code is automatically pushed to your GitHub repository or you can download the source code in a Zip file. You own your code.
From this point, you can use your favorite IDE to customize the code and add business logic. We also made it easy to modify your data models without overriding your custom code every time you re-generate your app, allowing your service to evolve with the business.
Would love to get your feedback and answer any question you have.
I’m Yuval, and for the past several years I’ve been building dev tools (some of you might know Amplication). Over that time, we’ve all seen the rise of AI copilots and agents. They are useful for individuals in the IDE, but limited when it comes to how teams actually ship software. I believe the next step is moving beyond copilots into *autonomous, continuous AI* that runs inside the SDLC itself.
That’s what we’re building with https://overcut.ai/. It connects directly to GitHub, Jira, and other tools, and runs workflows that handle things like:
- Reviewing PRs - Writing tests - Generating specs and docs - Triaging and resolving issues - Opening and updating PRs automatically
The difference is that instead of manually operated assistants or black box agents, you define the workflows (like CI/CD pipelines, but for AI agents). This makes it transparent and under your control.
We provide several ready-made playbooks, and you can also build your own for anything you can imagine on top of Git and tickets. There are built-in integrations to GitHub, GitLab, Bitbucket, Azure DevOps, and Jira.
Would love to hear your thoughts: what workflows would you want AI to take over, and what would hold you back from trusting something like this?
Thanks for reading