Kypso

A one-sentence summary

Kypso is an AI-driven process automation platform designed for software development teams; it used configurable AI Champions to connect code repositories, project management tools, and communication tools for the team. The product has now been acquired by Incredibuild, and when evaluating it it is necessary to consider its past capabilities separately from its current availability as a purchase option.

Tool Introduction

Founded in 2023 by former Snyk engineers Adam Gold and Tomer Ezer, Kypso aims to reduce the repetitive tasks that engineering managers and development teams have to handle in areas such as code review, task synchronization, communication regarding releases, and daily process management.

The focus of the platform’s design is not to replace programmers in writing all the code, but rather to enable AI agents to monitor events within the team’s existing tools, organize relevant context information, carry out various processes, and request human confirmation when necessary.

Current product status

In November 2025, Kypso was acquired by the software development acceleration platform Incredibuild; its founding team joined Incredibuild to work on developing AI-native development platforms. The Kypso website is still accessible, but the amount of public content available there has significantly decreased.

Historical product positioning

Kypso models engineering processes as executable workflows, and enables context-aware AI agents to carry out tasks such as classification, generation, reminders, and status synchronization across different collaboration systems. It is more akin to a platform for automating development operations rather than a regular chatbot.

• Provides specialized automated components for the software development process.
• Link events from tools such as GitHub, Jira, and Slack together.
• Use AI to perform classification, summarization, and the generation of structured content.
• Manual approval can be added before performing high-risk actions.
• Isolate different projects and integration configurations through team spaces.
• Provides process visibility and anomaly alerts for project managers.

Core competencies

Automation of engineering workflows

Teams can define trigger conditions and subsequent actions based on pull requests, issue tickets, Slack messages, releases, or incident events. AI is responsible for understanding unstructured information, while workflows handle delivering the results to the designated systems.

Context-aware AI agent

Kypso emphasizes the creation of context from code repositories, team practices, and organizational knowledge, with agents then involved in the specific processes. Compared to receiving just a single prompt, this approach is more suitable for ongoing development tasks.

Code Review Champion

The code review agent is used to monitor new pull requests, summarize code changes, identify issues of concern for the team, and provide feedback. The older version of this tool also offers the ability to alert users about outdated pull requests, organize unresolved discussions, and generate release notes.

Cross-tool collaboration

The platform can convert chat messages into project tasks, and it can also push code and task progress back to the team channels. This reduces the need to manually copy information between communication tools, code hosting services, and issue tracking systems.

Manual approval

For actions such as creating tasks, modifying production data, or sending notifications, the workflow can first send suggestions to Slack for manual approval. This design helps reduce the risk of agents making mistakes that could affect real projects.

Code review process

1. The connection team needs to review the code repository.
2. Select the repository, branch, and pull request events that you want to monitor.
3. Configure the types of defects, code standards, and alert conditions that are of concern to the team.
4. The agent reads the code changes and related context to generate a summary.
5. Submit issues, suggestions, or matters requiring manual attention in a pull request.
6. Push outdated requests and unresolved discussions to the relevant members.
7. After reviewing the manual feedback, a decision is made to modify, merge, or ignore it.
8. Regularly check for false positives, false negatives, and permission scopes, and adjust the rules accordingly.

Example of engineering process

Supported collaboration systems

The acquisition announcement specifies that Kypso integrates context-aware agents into GitHub, Jira, and Slack. Previous content also demonstrated workflows across different tools, but there is no current catalog of connectors available to confirm all the integrations.

Which users are it suitable for

• Engineering managers who need to reduce the workload related to process tracking.
• Software development teams that wish to speed up the feedback on pull requests.
• Technology companies that need to synchronize product, engineering, and support information.
• Teams that frequently create defects or requirements from Slack messages.
• A person in charge is needed to automatically generate release notes and progress summaries.
• Organizations that wish to introduce AI agents for manual approval into their R&D processes.
• Enterprise customers are evaluating Incredibuild’s future AI development platform.

Which needs it is not suitable for

• Developers who only need code completion or chat-based Q&A are sufficient.
• Teams that require immediate purchase and must have transparent, self-service pricing.
• Projects that can only be purchased after obtaining complete and publicly available API documentation.
• Organizations that require a completely open-source core platform that can be deployed on their own.
• Environments in which no access rights can be granted to code repositories or collaboration systems.
• I hope for an AI system that can automatically merge all the code without the need for manual review.

Preparations before use

1. First, verify whether Kypso’s standalone service still accepts new clients.
2. Ask the service provider for the products available after the acquisition, as well as support and migration arrangements.
3. List the specific engineering processes that need to be automated and the responsible persons.
4. Determine the minimum permissions required for GitHub, Jira, and Slack.
5. Select low-risk processes that are easy to verify manually for piloting.
6. Establish mechanisms for false alarms, failures, timeouts, and manual intervention.
7. Confirm the rules for data processing, storage, deletion, and model training.
8. Use real but non-sensitive items to verify output quality and process stability.
9. After the assessment is successful, expand the warehouse, the team, and the scope of automation.

Pricing and purchase status

The price information was verified on August 23, 2026; the actual amounts, taxes, exchange rates, and discounts may vary, and the final figures will be those displayed on the settlement page.

Kypso currently does not have an independent, publicly available pricing page that can be verified; therefore, it is not possible to use information regarding the previous free version, the team version, or the pricing based on the Champion plan as indications of current prices. The business model following the acquisition, the billing structure, and the renewal terms for existing customers all need to be determined separately.

Purchase and Migration Checklist

1. Verify whether independent Kypso tenants can still create and renew subscriptions.
2. Confirm whether the existing data, configurations, and workflows should be retained.
3. Verify whether code review Champion is still provided independently.
4. Obtain the accurate price, billing unit, quota, and contract duration.
5. Confirm the support team, service level, and fault response channels.
6. Confirm whether to migrate to Incredibuild and the corresponding timeline.
7. Verify whether the permissions of the connector and the party responsible for data processing have changed after the migration.
8. Confirm the arrangements for data export and deletion at the time of service termination.
9. The functions promised and the rights related to migration are recorded in the signing documents.

APIs and developer capabilities

No current APIs, SDKs, or comprehensive development documentation provided by Kypso for use by the public have been identified. Integrations with GitHub, Jira, and Slack are part of the product’s connectivity features; these cannot be used as evidence to conclude that users can develop their own clients using open APIs.

Open-source status

The Kypso core platform, AI Champions, and the managed backend are not open-source projects; furthermore, no official core code repository belonging to Kypso has been identified. The existence of a connection to a GitHub repository does not mean that the product’s source code is available publicly.

Privacy and security

Kypso needs access to code repositories, task management systems, and team communication tools; it may also have access to source code, information on defects, customer issues, as well as internal communications. No separate privacy and security pages specific to Kypso were identified following the acquisition, and companies should not base their purchasing decisions on old commitments.

• Only the permissions for the warehouses and channels required to complete the pilot are granted.
• Prevent agents from accessing unrelated private repositories and sensitive channels.
• Verify whether the data is used for model training or product improvement.
• Confirm the data storage area, encryption, retention, and deletion periods.
• Request sub-processors, certification reports, and incident notification mechanisms.
• Verify whether the permissions of the original system can be fully inherited by the proxy.
• Enable manual approval for creating tasks, adding comments, and modifying data.
• Regularly rotate tokens and revoke connections that are no longer in use.
• During the acquisition and migration process, the identities of the controllers and processors are re-verified.

Product advantages

• It is designed around real engineering processes, rather than a generic chat interface.
• Access the team’s existing working environment through GitHub, Jira, and Slack.
• It can handle unstructured contexts such as messages, ticket requests, and code changes.
• The combination of workflows and manual approval is suitable for teams with defined responsibility boundaries.
• Code review, task synchronization, and release communication form a continuous process.
• Knowledge graphs and team context are important design aspects of a product.
• After being acquired by Incredibuild, it has the potential to be integrated into larger development platforms.

Main limitations

• The current registration and purchase status of standalone products is not clear enough.
• The public pricing page, as well as the current packages and quotas, are not available.
• The functions to be retained after the acquisition, the migration process, and the roadmap have not been fully made public.
• The retention of the brand’s website does not mean that all previous functionalities will continue to be available.
• No public APIs, SDKs, or complete development documentation were found.
• The core platform is not open-source, so it is not possible to deploy it manually or audit all of its code.
• Connecting to engineering systems requires high levels of permission and poses data risks.
• AI code review may generate false positives, false negatives, or suggestions that do not conform to team standards.
• When handling cross-system actions, proxy processing still requires permission control and manual review.
• Old prices, old packages, and information from third-party catalogs may no longer be valid.

Frequently Asked Questions

Can Kypso still be used?

The brand page is still available, but the information regarding public registration, pricing, and the status of independent services cannot be confirmed with certainty. New users should first contact the relevant team for clarification, rather than attempting to set up everything using the old instructions.

Who acquired Kypso?

Kypso was acquired by Incredibuild in November 2025, and its founding team joined Incredibuild to work on developing an AI-native software development platform.

What problem does Kypso mainly address?

It primarily automates code review, task synchronization, chat message handling, communication for releases, and tracking of development processes, thereby helping project managers reduce the effort required for coordinating different tools.

Which tools does Kypso support?

GitHub, Jira, and Slack are the key integrations explicitly mentioned in the acquisition details. Whether existing connection capabilities such as those provided by Linear will continue to be available depends on the current account or contract terms.

Is there a free version of Kypso?

Historical records indicate that free or trial versions were available, but there is currently no valid public pricing page that confirms such options are still offered. The old plans should not be used as a basis for current registration or purchase.

Does Kypso provide an API?

Currently, no existing API and SDK documentation available for the public has been identified. The ability of a product to connect to third-party systems does not mean that it offers open development interfaces.

Is Kypso an open-source tool?

No, the core platform and AI Champions have not been released as open-source projects, nor is there any verifiable official self-deployment version available.

Can code review replace human effort?

It is not recommended to replace human review entirely. AI is suitable for generating summaries, checking common issues, and providing reminders, but the design, security, business logic, and the final integration should still be determined by qualified personnel.

Summary

Kypso represents a category of context-aware AI agents designed for development operations: it connects code, tasks, and communication events, enabling code reviews, issue tracking, release notes, and team synchronization to be carried out automatically within a unified process.

It is now more suitable as a record of acquired products and technical capabilities, rather than an independent tool with transparent pricing that allows for immediate self-purchase. Before adopting it, it is necessary to clarify the existing services, the migration process, contract prices, data governance measures, and the plans regarding future Incredibuild products.