Integrations
Source in from where it lives. Specs out to where teams work.
PYD ENTERPRISES reads from Git and Endevor inside your network and writes open-standard specifications to the trackers, wikis, API tools and decision engines your modernization program already runs.
12 of 12 integrations
GitHub
Source control
Mirror GitHub or GitHub Enterprise Server repositories inside your VPC, scan a pinned commit, and return specifications to a review repository as pull requests.
Ingest and exportGitLab
Source control
Clone self-managed GitLab projects inside your network, run PYD ENTERPRISES as a CI job on your own runners, and publish specs back as merge requests.
Ingest and exportBitbucket
Source control
Ingest legacy repositories from Bitbucket Data Center or Bitbucket Cloud with read-only credentials, and return specification bundles as pull requests for review.
Ingest and exportAzure DevOps
Source control
Scan Azure Repos Git repositories and TFVC snapshots from Azure DevOps Server or Services, run scans from self-hosted pipeline agents, and export specs as pull requests.
Ingest and exportBroadcom Endevor
Mainframe SCM
Ingest exported Endevor element libraries (COBOL, copybooks, JCL, PROCs and BMS maps) with their environment, system, subsystem, type and stage metadata intact.
IngestJira
Work tracking
Turn every rule flagged for review into a Jira issue with source location, extracted logic and reviewer, so sign-off happens in the tracker your program already runs on.
ExportConfluence
Documentation
Publish a living specification space per legacy system: rule inventory, data dictionary, interface catalog and diagrams, regenerated on each approved scan.
ExportPostman
API tooling
Export Postman Collection v2.1 files with one request per synthesized operation, example bodies drawn from equivalence fixtures, and test scripts that assert legacy outputs.
ExportSwaggerHub
API tooling
Publish synthesized OpenAPI definitions to SmartBear SwaggerHub so API governance, style rules and versioning apply to specs extracted from legacy code.
ExportCamunda
Decision engines
Import PYD ENTERPRISES' DMN decision tables into Camunda so extracted legacy rules can be modeled, tested and executed in the target architecture.
ExportDrools
Decision engines
Run extracted legacy rules on the Drools DMN engine in Java services, with DMN files packaged alongside the code and verified against legacy fixtures.
ExportBackstage
Developer portal
Register legacy systems, their extracted APIs and their dependencies in your Backstage software catalog with generated catalog-info.yaml and API entities.
Export
Two directions
What goes in, and what comes out.
Ingest
Source and metadata enter PYD ENTERPRISES inside your network: Git mirrors pinned to a commit, Endevor element exports with their inventory location, DDL and CICS definitions. Credentials are read-only.
Export
Approved specifications leave PYD ENTERPRISES as open-standard files or tracker items: pull requests with OpenAPI and DMN, Jira review issues, Confluence pages, Postman collections, DMN for decision engines and catalog descriptors.
Never
The source tree, ASTs and symbol graph never leave your environment through any integration. Excerpts in exported items are optional and off by default for externally hosted tools.
FAQ
Integration questions.
Do integrations send our source code outside our network?
Ingest integrations pull code into PYD ENTERPRISES inside your environment. Export integrations send generated specifications, never the source tree. When a destination such as Jira or Confluence is hosted outside your network, you choose whether source excerpts may appear in what is exported, and you can switch them off entirely.
Are these official vendor partnerships?
No. These integrations use the standard interfaces and file formats each tool already supports (Git, Collection v2.1, DMN XML, OpenAPI, catalog descriptor files, REST interfaces for issues and pages). They do not depend on a vendor partnership or a marketplace app.
What if our tool is not listed?
Every PYD ENTERPRISES export is an open-standard file: OpenAPI 3.1, AsyncAPI 2.6, DMN 1.5, JSON Schema 2020-12, Postman 2.1, Mermaid and PlantUML. Most API, documentation and decision tools can read them without a dedicated integration.
Do integrations work in an air-gapped deployment?
Yes, with file-based routes. Git bundles and Endevor exports come in on approved media; specification bundles, CSV review queues and static documentation go out the same way. Nothing requires PYD ENTERPRISES to reach the internet.
Plug discovery into the program you already run.
Run PYD ENTERPRISES on 100,000 lines of COBOL or Java in your private VPC and review OpenAPI specs and DMN tables tomorrow.