Penske Signals
A diversified transportation services conglomerate operating truck leasing, logistics, automotive retail, and professional motorsports across North America. Penske Corporation spans Penske Truck Leasing, Penske Logistics, Penske Automotive Group, and Team Penske with 73,000+ employees and $43B+ in consolidated revenue.
This is a Naftiko Signals read of Penske’s technology and AI investment posture — mined from public workforce signals (job postings, press releases, newsroom content) and matched against Naftiko’s curated vocabulary of services, tools, concepts, and standards across the 44 Naftiko signal groups.
For Penske we detected 568 areas, 57 services, 29 tools, and 47 standards — producing a total signal score of 651.
How to read this page: Impact Report is the narrative read-out. Capabilities are Naftiko agent workflows you could ship on top of Penske’s existing stack — each one runnable in the Naftiko Framework. Navigation ranks the next moves we’d recommend, grouped by theme. Signals is the score breakdown across every Naftiko signal group, each row linking to its definition. Areas, Services, Tools, and Standards are the raw detections behind the score. Why? explains the methodology and audience.
Penske Technology Investment Impact Report
| Prepared by Naftiko | April 2026 |
Executive Summary
This report presents a signal-based analysis of Penske’s technology investment posture, derived from Naftiko’s methodology of examining services deployed, tools adopted, concepts referenced, and standards followed across workforce signals. The analysis spans foundational infrastructure, data platforms, customization capabilities, operational efficiency, productivity, integration, governance, economics, and strategic alignment.
A diversified transportation services conglomerate operating truck leasing, logistics, automotive retail, and professional motorsports across North America. Penske Corporation spans Penske Truck Leasing, Penske Logistics, Penske Automotive Group, and Team Penske with 73,000+ employees and $43B+ in consolidated revenue.
The assessment yields a total signal score of 651 across 41 dimensions. The six strongest signal categories are data (65), services (57), operations (40), cloud (39), automation (29), roiBusinessMetrics (28).
Layer 1: Foundational Layer
Evaluating Penske’s foundational capabilities across Artificial Intelligence, Cloud, Open-Source, Languages, and Code — the core infrastructure and development building blocks supporting Transportation / Logistics and Automotive / Truck Leasing & Rental and Automotive / Truck Leasing & Fleet Services operations.
Waves: Large Language Models (LLMs), Generative Pre-trained Transformer (GPT), Open-Source LLMs
Artificial Intelligence — Score: 22 #9/27
Penske’s AI score of 22 reflects adoption across limited recorded signals.
- Concepts: Agentic AI, Agentic Solutions, Agentics, Artificial Intelligence, Artificial Intelligence/Machine Learning, Generative AI, Machine Learning, Machine Learning Algorithms
- Standards: MLOps
AI posture sets the ceiling on downstream AI workloads at Penske.
Cloud — Score: 39 #6/27
Cloud score of 39 spans Amazon Web Services, Azure Active Directory, CloudFormation alongside IaC tooling (Buildpacks, Docker, Kubernetes).
- Services: Amazon Web Services, Azure Active Directory, CloudFormation, Google Cloud Platform, Microsoft Azure
- Tools: Buildpacks, Docker, Kubernetes, Terraform
- Concepts: Cloud Architectures, Cloud Computing, Cloud Computing Platforms, Cloud Connectivity, Cloud Data, Cloud Data Platforms, Cloud Database Technologies, Cloud Databases
Cloud maturity is the anchor for scaling AI workloads at Penske.
Open-Source — Score: 10 #8/27
Open-Source score of 10 anchored on limited recorded signals.
- Tools: Angular, Apache AGE, Apache Airflow, Apache Flex, Apache JMeter, Apache Kafka, Apache Phoenix, Apache Pivot
- Concepts: Contributions, Open Source
- Standards: CODE_OF_CONDUCT.md, CONTRIBUTORS.md, LICENSE.md
Consumption is broad; formal contribution posture is an opportunity area.
Languages — Score: 14 #9/27
Languages score of 14 across CSS, Go, Java, Move, Visual Basic.
- Languages: CSS, Go, Java, Move, Visual Basic
Language mix is a revealing signal of Penske’s engineering history and modernization priorities.
Code — Score: 22 #10/27
Code score of 22 anchored on limited recorded signals.
- Tools: PowerShell
- Concepts: Application Programming Interfaces, Code Management, Code Quality, Code Reviews, Continuous Integration/Continuous Deployments, DevOps Practices, Infrastructure As Codes, Programming
- Standards: DevOps
Developer tooling is the lever for compound productivity via AI coding assistants.
Layer Summary: Penske’s Foundational Layer reflects AI (22), Cloud (39), Open-Source (10), Languages (14), and Code (22) — the bedrock on which every subsequent AI-readiness capability is built.
Layer 2: Retrieval & Grounding
Evaluating Penske’s data and retrieval capabilities — Data, Databases, Virtualization, Specifications, Context Engineering — that ground AI workloads in enterprise information.
Waves: Vector Databases, Retrieval-Augmented Generation (RAG), Prompt Engineering, Context Engineering
Data — Score: 65 #7/27
Data score of 65 reflects Alteryx, Power BI, Power Query.
- Services: Alteryx, Power BI, Power Query, Snowflake, Splunk, Tableau Desktop
- Tools: Apache Airflow, Apache Kafka, Apache Spark, R
- Concepts: Business Analytics, Customer Analytics, Data Analysis, Data Analytics, Data Analytics Tools, Data Governance, Data Management, Data Pipelines
- Standards: Data Modeling, Data Models
Analytical depth is the foundation for retrieval-augmented AI.
Databases — Score: 12 #7/27
Databases score of 12 spans Oracle, Snowflake.
- Services: Oracle, Snowflake
- Concepts: Cloud Database Technologies, Cloud Databases, Database Management, Database Technologies, Databases, NoSQL, Relationals, SQL Databases
- Standards: SQL
Portfolio rationalization is an ongoing lever.
Virtualization — Score: 8 #10/27
Virtualization score of 8 on Solaris Zones, Docker, Kubernetes.
- Services: Solaris Zones
- Tools: Docker, Kubernetes
- Concepts: Container Orchestration, Containerization, Containerization Technologies, Containers
Containerization paired with VMs is a pragmatic stance.
Specifications — Score: 2 #12/27
Specifications score of 2 rooted in REST/HTTP/JSON.
- Concepts: API Gateways, API Management, Application Programming Interfaces
- Standards: HTTP, REST, TCP/IP, XML
Formalizing OpenAPI as enterprise standard is a prerequisite for AI agent integration.
Context Engineering
Penske’s Context Engineering investment is emerging.
Pairing strong Data with formal context layer is the highest-leverage AI readiness move.
Layer Summary: Penske’s Retrieval posture is shaped by Data (65), Databases (12), and Specifications (2).
Layer 3: Customization & Adaptation
Evaluating Penske’s capabilities for customizing AI to its business — Data Pipelines, Model Registry, Multimodal Infrastructure, Domain Specialization.
Waves: Fine-Tuning & Model Customization, Multimodal AI
Data Pipelines — Score: 14 #4/27
Data Pipelines score of 14 reflects Apache Airflow, Apache Kafka, Apache Spark.
- Tools: Apache Airflow, Apache Kafka, Apache Spark
- Concepts: Continuous Integration/Continuous Deployments, Data Integrations, Data Pipelines, Extract Transform Loads, Integration Workflows, Integrations
Streaming pipelines prerequisite for real-time AI inference.
Model Registry & Versioning — Score: 2 #13/27
Model Registry score of 2 via limited recorded signals.
- Standards: MLOps
Enterprise registry with approvals is prerequisite for regulated AI.
Multimodal Infrastructure — Score: 2 #11/27
Multimodal score of 2 via limited recorded signals.
- Concepts: Generative AI
Centralized OCR/audio/image extractors improve AI project productivity.
Domain Specialization — Score: 0
Domain Specialization score of 0.
Industry-specific fine-tuning is a differentiated long-term capability for Penske.
Layer Summary: Customization bridges generic AI and business-specific advantage.
Layer 4: Efficiency & Specialization
Evaluating Penske’s operational efficiency and platform layer — Automation, Containers, Platform, Operations.
Waves: Small Language Models (SLMs), Model Routing / Orchestration, Reasoning Models
Automation — Score: 29 #7/27
Automation score of 29 reflects Make, Microsoft Power Automate.
- Services: Make, Microsoft Power Automate
- Tools: Apache Airflow, PowerShell
- Concepts: Automation, Business Process Automation, Integration Workflows, Process Automation, Warehouse Automation, Workflows
Automation footprint is ready for AI augmentation on high-toil processes.
Containers — Score: 13 #5/27
Containers score of 13 on Buildpacks, Docker, Helm.
- Tools: Buildpacks, Docker, Helm, Kubernetes
- Concepts: Container Orchestration, Containerization, Containerization Technologies, Containers
Container-native AI deployment is the logical next step.
Platform — Score: 15 #8/27
Platform score of 15 spans Amazon Web Services, Azure Active Directory, Google Cloud Platform.
- Services: Amazon Web Services, Azure Active Directory, Google Cloud Platform, Microsoft Azure, SAP, SAP BI
- Concepts: AI Platforms, Cloud Computing Platforms, Cloud Data Platforms, Cloud Platforms, Customer Data Platforms, Data Platforms, Machine Learning Platforms, Platform Engineering
Platform engineering maturity is the next milestone.
Operations — Score: 40 #6/27
Operations score of 40 anchored on Datadog, Dynatrace, Splunk.
- Services: Datadog, Dynatrace, Splunk
- Tools: Prometheus, Terraform
- Concepts: Business Operations, Incident Management, Incident Responses, Operational Excellence, Operations Management, Operations Researches, Service Operations
Operational tooling is a foundation for AI-driven SRE.
Layer Summary: Automation (29) and Operations (40) are direct levers for AI-augmented productivity.
Layer 5: Productivity
Evaluating Penske’s productivity tooling — SaaS, Services, Code.
Waves: Coding Assistants, Copilots
Software As A Service (SaaS) — Score: 8 #9/27
SaaS score of 8 includes Box, Microsoft Teams.
- Services: Box, Microsoft Teams
Rationalization and unified auth are the optimization opportunities.
Code — Score: 22 #10/27
Code anchored on limited recorded signals.
- Tools: PowerShell
- Concepts: Application Programming Interfaces, Code Management, Code Quality, Code Reviews, Continuous Integration/Continuous Deployments, DevOps Practices, Infrastructure As Codes, Programming
- Standards: DevOps
Wiring coding assistants creates compound productivity gains.
Services — Score: 57 #10/27
Services score of 57 spans Penske’s full service portfolio.
- Services: Adobe Launch, Alteryx, Amazon Web Services, Apple, Azure Active Directory, Box, CloudFormation, Datadog
Scale of services drives the integration-layer imperative.
Layer Summary: Services score of 57 reflects Penske’s breadth of enterprise SaaS consumption.
Layer 6: Integration & Interoperability
Evaluating Penske’s API, integration, event-driven connectivity.
Waves: MCP (Model Context Protocol), Agents, Skills
API — Score: 12 #7/27
API score of 12; concepts: API Gateways, API Management.
- Concepts: API Gateways, API Management
- Standards: HTTP, REST
Formalizing API standards is the most impactful integration move.
Integrations — Score: 20 #5/27
Integrations score of 20 spans limited recorded signals.
- Concepts: Continuous Integration/Continuous Deployments, Data Integrations, Integration Workflows, Integrations
- Standards: Enterprise Integration Patterns
iPaaS reduces integration debt.
Event-Driven — Score: 6 #6/27
Event-Driven score of 6.
- Tools: Apache Kafka
- Concepts: Events, Stream Processing
Event streaming is foundational for real-time AI.
Patterns — Score: 12 #6/27
Patterns score of 12 on Spring Framework.
- Tools: Spring Framework
- Concepts: Microservices, Patterns
Microservice patterns support AI workload scaling.
Specifications — Score: 2 #12/27
Specifications score of 2.
- Concepts: API Gateways, API Management, Application Programming Interfaces
- Standards: HTTP, REST, TCP/IP, XML
Elevating OpenAPI to enterprise standard creates shared vocabulary for AI.
Apache — Score: 10 #6/27
Apache score of 10: Apache AGE, Apache Airflow, Apache Flex, Apache JMeter, Apache Kafka.
- Tools: Apache AGE, Apache Airflow, Apache Flex, Apache JMeter, Apache Kafka, Apache Phoenix, Apache Pivot, Apache Spark
Apache ecosystem depth is a characteristic enterprise strength.
CNCF — Score: 8 #6/27
CNCF score of 8: Buildpacks, Kubernetes, Prometheus.
- Tools: Buildpacks, Kubernetes, Prometheus
CNCF maturity pairs with Kubernetes adoption.
Layer Summary: API (12) and Integrations (20) are the connective tissue for scaling AI.
Layer 7: Statefulness
Evaluating Penske’s Observability, Governance, Security, Data handling.
Waves: Memory Systems
Observability — Score: 22 #6/27
Observability score of 22 spans Datadog, Dynatrace, Splunk.
- Services: Datadog, Dynatrace, Splunk
- Tools: Prometheus
- Concepts: Alerting, Logging, Monitoring, Observability, Observability Tools
Consolidation lowers cost.
Governance — Score: 23 #13/27
Governance score of 23; standards: GDPR, ISO, OSHA.
- Concepts: AI Governance, Audits, Compliance, Data Governance, Governance, Governance Frameworks, Internal Controls
- Standards: GDPR, ISO, OSHA, Six Sigma
Extending to AI governance is the natural evolution.
Security — Score: 19 #11/27
Security score of 19 anchored on limited recorded signals.
- Concepts: Authentications, Authorizations, Security Best Practices, Security Requirements
- Standards: IAM, ISO, PCI Compliance, SSO
AI-specific security is a required add to existing program.
Data — Score: 65 #7/27
Data — Alteryx, Power BI, Power Query anchors.
- Services: Alteryx, Power BI, Power Query, Snowflake, Splunk, Tableau Desktop
- Tools: Apache Airflow, Apache Kafka, Apache Spark, R
- Concepts: Business Analytics, Customer Analytics, Data Analysis, Data Analytics, Data Analytics Tools, Data Governance, Data Management, Data Pipelines
- Standards: Data Modeling, Data Models
Continued cataloging and lineage pays off at AI scale.
Layer Summary: Observability (22), Governance (23), Security (19) reflect Penske’s operational maturity.
Layer 8: Measurement & Accountability
Evaluating Penske’s measurement discipline — Testing, Observability, DevEx, ROI.
Waves: Evaluation & Benchmarking
Testing & Quality — Score: 8 #14/27
Testing score of 8 with Selenium.
- Tools: Selenium
- Concepts: Acceptance Testing, Automated Testing, Performance Testing, QA, Test Instruments, Test Strategies, Testing Frameworks, Testing Strategies
- Standards: Acceptance Criteria, Six Sigma
AI-specific evals extend traditional testing.
Observability — Score: 22 #6/27
Observability — Datadog, Dynatrace, Splunk.
- Services: Datadog, Dynatrace, Splunk
- Tools: Prometheus
- Concepts: Alerting, Logging, Monitoring, Observability, Observability Tools
Instrumented for AI workload observation.
Developer Experience — Score: 6 #12/27
DevEx score of 6 on limited recorded signals.
- Tools: Docker
DORA metrics and IDPs are next investments.
ROI & Business Metrics — Score: 28 #6/27
ROI score of 28 reflects Alteryx, Power BI, SAP.
- Services: Alteryx, Power BI, SAP, Tableau Desktop
- Concepts: Androids, Business Analytics, Financial Analysis, Financial Data, Financial Management, Financial Models, Financial Plannings, Financial Policies
ROI discipline translates naturally to AI initiatives.
Layer Summary: Measurement is necessary for accountable AI initiatives.
Layer 9: Governance & Risk
Evaluating Penske’s Regulatory, AI Review, Security, Governance, Privacy controls.
Waves: Governance & Compliance
Regulatory Posture — Score: 11 #9/27
Regulatory score of 11 with standards: GDPR, ISO, OSHA.
- Concepts: Compliance, Legal
- Standards: GDPR, ISO, OSHA, PCI Compliance
Proactive alignment with NIST AI RMF is a forward investment.
AI Review & Approval — Score: 11 #12/27
AI Review score of 11 with limited recorded signals.
- Concepts: AI Platforms
- Standards: MLOps
Formalized AI review council is the priority governance investment.
Security — Score: 19 #11/27
Security — limited recorded signals.
- Concepts: Authentications, Authorizations, Security Best Practices, Security Requirements
- Standards: IAM, ISO, PCI Compliance, SSO
AI threat model coverage extends existing security.
Governance — Score: 23 #13/27
Governance standards: GDPR, ISO, OSHA.
- Concepts: AI Governance, Audits, Compliance, Data Governance, Governance, Governance Frameworks, Internal Controls
- Standards: GDPR, ISO, OSHA, Six Sigma
AI governance as first-class discipline is the next step.
Privacy & Data Rights — Score: 3 #16/27
Privacy score of 3.
- Standards: GDPR
Formal ‘training-eligible?’ classification prevents inadvertent PII use in models.
Layer Summary: Security (19), Governance (23), AI Review (11) shape the AI compliance envelope.
Layer 10: Economics & Sustainability
Evaluating Penske’s AI FinOps, Provider Strategy, Partnerships, Talent, Data Centers.
Waves: Cost Economics & FinOps, Supply Chain & Dependency Risk, Data Centers
AI FinOps — Score: 2 #13/27
AI FinOps score of 2 with Amazon Web Services, Azure Active Directory, Google Cloud Platform.
- Services: Amazon Web Services, Azure Active Directory, Google Cloud Platform, Microsoft Azure
- Concepts: Cost Accounting, Cost Management, Financial Plannings
Token-cost tagging required before AI spend accelerates.
Provider Strategy — Score: 6 #13/27
Provider Strategy score of 6 with Amazon Web Services, Google Cloud Platform, Microsoft, Microsoft 365.
- Services: Amazon Web Services, Google Cloud Platform, Microsoft, Microsoft 365, Microsoft Azure, Microsoft Edge, Microsoft Entra, Microsoft Exchange
- Concepts: Supplier Management
Explicit provider strategy tightens AI partnership decisions.
Partnerships & Ecosystem — Score: 21 #9/27
Partnerships score of 21 with Amazon Web Services, Google, Google Analytics, Google Apps Script.
- Services: Amazon Web Services, Google, Google Analytics, Google Apps Script, Google Campaign Manager, Google Cloud Platform, Google Drive, Google Maps
AI-specific partnerships are emerging.
Talent & Organizational Design — Score: 23 #10/27
Talent score of 23 with limited recorded signals.
- Concepts: Artificial Intelligence/Machine Learning, Human Resources, Learning, Machine Learning, Machine Learning Algorithms, Machine Learning Models, Machine Learning Platforms, Professional Trainings
Aligning talent toward AI skill development is direct leverage.
Data Centers
Data Centers investment signals are limited.
Hybrid-cloud vs public-cloud becomes a board-level question at AI scale.
Layer Summary: Talent (23) and Partnerships (21) most affect AI outcomes.
Layer 11: Storytelling & Entertainment & Theater
Evaluating Penske’s strategic narrative — Alignment, Standardization, M&A, Experimentation.
Waves: Moltbook, Gastown, Ralph Wiggum, OpenClaw / Clawdbot, Artificial General Intelligence (AGI)
Alignment — Score: 8 #13/27
Alignment score of 8; concepts: Application Architectures, Architectures, Cloud Architectures.
- Concepts: Application Architectures, Architectures, Cloud Architectures, Data Architectures, Data Transformations, Digital Transformations, Network Architectures, System Architectures
- Standards: Agile Methodology
Aligning AI to business outcomes makes AI accountable.
Standardization — Score: 12 #10/27
Standardization score of 12: ISO, REST, SQL, Standard Operating Procedures.
- Standards: ISO, REST, SQL, Standard Operating Procedures
Extending to AI (model cards, eval suites) is a natural evolution.
Mergers & Acquisitions — Score: 6 #13/27
M&A score of 6.
- Concepts: Due Diligences, Financial Models, Talent Acquisition
AI-capability acquisitions can accelerate gaps.
Experimentation & Prototyping
Experimentation & Prototyping signals are limited.
A named internal AI sandbox reduces shadow-AI risk.
Layer Summary: Alignment (8) and Standardization (12) shape AI program direction.
Strategic Assessment
Top Three 2026 Investment Recommendations for Penske
-
Establish an API-First Integration Layer. API score of 12 across 57 services leaves Penske without reusable connective tissue. Prioritize API standards, deploy an enterprise gateway, publish a service catalog.
-
Stand Up a Formal AI Governance and Review Council. AI Review score of 11 combined with AI adoption (score 22) creates regulatory and reputational risk. Charter a council, publish review criteria, gate production AI.
-
Invest in Real-Time Data Pipelines and Event Streams. Data Pipelines (14) and Event-Driven (6) are the gap between data platform maturity and real-time AI. Extend Kafka or Azure Event Hubs to critical flows first.
Methodology
Scores derive from the density and diversity of signals detected across Services, Tools, Concepts, and Standards, aggregated into 11 strategic layers mapping the full technology stack.
Based on signal data available as of April 2026.
Capabilities are Naftiko definitions for how enterprise services, tools, and standards can be combined to deliver business value using AI. Each capability below defines the integrations, workflows, and orchestrations available — run them with the Naftiko Framework or browse the shipped set in the Naftiko Fleet.
Access Review Campaign Generation — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Access Review Campaign Generation
description: Access Review Campaign Generation — contextualized for Penske based on its actual service and tool footprint.
tags:
- servicenow
- automation
capability:
exposes:
- type: mcp
namespace: access-review
port: 8080
tools:
- name: execute
description: Access Review Campaign Generation — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: access-review.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: access-review
baseUri: https://penske.internal.example.com/access-review/v1
authentication:
type: bearer
token: $secrets.access_review_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Accounts Payable Invoice Approval Routing — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Accounts Payable Invoice Approval Routing
description: Accounts Payable Invoice Approval Routing — contextualized for Penske based on its actual service and tool footprint.
tags:
- oracle
- automation
capability:
exposes:
- type: mcp
namespace: ap-approval
port: 8080
tools:
- name: execute
description: Accounts Payable Invoice Approval Routing — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: ap-approval.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: ap-approval
baseUri: https://penske.internal.example.com/ap-approval/v1
authentication:
type: bearer
token: $secrets.ap_approval_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Adobe Campaign Launch Readiness Check — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Adobe Campaign Launch Readiness Check
description: Adobe Campaign Launch Readiness Check — contextualized for Penske based on its actual service and tool footprint.
tags:
- adobe-campaign
- automation
capability:
exposes:
- type: mcp
namespace: campaign-ready
port: 8080
tools:
- name: execute
description: Adobe Campaign Launch Readiness Check — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: campaign-ready.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: campaign-ready
baseUri: https://penske.internal.example.com/campaign-ready/v1
authentication:
type: bearer
token: $secrets.campaign_ready_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
APM Latency Spike Investigation — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: APM Latency Spike Investigation
description: APM Latency Spike Investigation — contextualized for Penske based on its actual service and tool footprint.
tags:
- datadog
- automation
capability:
exposes:
- type: mcp
namespace: apm-spike
port: 8080
tools:
- name: execute
description: APM Latency Spike Investigation — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: apm-spike.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: apm-spike
baseUri: https://penske.internal.example.com/apm-spike/v1
authentication:
type: bearer
token: $secrets.apm_spike_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Azure DevOps Work Item Auto-Link — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Azure DevOps Work Item Auto-Link
description: Azure DevOps Work Item Auto-Link — contextualized for Penske based on its actual service and tool footprint.
tags:
- azure-devops
- automation
capability:
exposes:
- type: mcp
namespace: ado-link
port: 8080
tools:
- name: execute
description: Azure DevOps Work Item Auto-Link — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: ado-link.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: ado-link
baseUri: https://penske.internal.example.com/ado-link/v1
authentication:
type: bearer
token: $secrets.ado_link_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Budget vs Actual Variance Explainer — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Budget vs Actual Variance Explainer
description: Budget vs Actual Variance Explainer — contextualized for Penske based on its actual service and tool footprint.
tags:
- sap
- automation
capability:
exposes:
- type: mcp
namespace: variance
port: 8080
tools:
- name: execute
description: Budget vs Actual Variance Explainer — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: variance.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: variance
baseUri: https://penske.internal.example.com/variance/v1
authentication:
type: bearer
token: $secrets.variance_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Change Management Request Triage — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Change Management Request Triage
description: Change Management Request Triage — contextualized for Penske based on its actual service and tool footprint.
tags:
- servicenow
- automation
capability:
exposes:
- type: mcp
namespace: change-mgmt
port: 8080
tools:
- name: execute
description: Change Management Request Triage — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: change-mgmt.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: change-mgmt
baseUri: https://penske.internal.example.com/change-mgmt/v1
authentication:
type: bearer
token: $secrets.change_mgmt_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
CI/CD Failure Observability Chain — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: CI/CD Failure Observability Chain
description: CI/CD Failure Observability Chain — contextualized for Penske based on its actual service and tool footprint.
tags:
- github
- automation
capability:
exposes:
- type: mcp
namespace: ci-failure
port: 8080
tools:
- name: execute
description: CI/CD Failure Observability Chain — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: ci-failure.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: ci-failure
baseUri: https://penske.internal.example.com/ci-failure/v1
authentication:
type: bearer
token: $secrets.ci_failure_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Conduct Quarterly Technology Posture Review — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Conduct Quarterly Technology Posture Review
description: Conduct Quarterly Technology Posture Review — contextualized for Penske based on its actual service and tool footprint.
tags:
- enterprise
- automation
capability:
exposes:
- type: mcp
namespace: posture-review
port: 8080
tools:
- name: execute
description: Conduct Quarterly Technology Posture Review — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: posture-review.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: posture-review
baseUri: https://penske.internal.example.com/posture-review/v1
authentication:
type: bearer
token: $secrets.posture_review_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Daily General Ledger Close Check — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Daily General Ledger Close Check
description: Daily General Ledger Close Check — contextualized for Penske based on its actual service and tool footprint.
tags:
- sap
- automation
capability:
exposes:
- type: mcp
namespace: gl-close
port: 8080
tools:
- name: execute
description: Daily General Ledger Close Check — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: gl-close.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: gl-close
baseUri: https://penske.internal.example.com/gl-close/v1
authentication:
type: bearer
token: $secrets.gl_close_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Data Quality SLO Check — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Data Quality SLO Check
description: Data Quality SLO Check — contextualized for Penske based on its actual service and tool footprint.
tags:
- snowflake
- automation
capability:
exposes:
- type: mcp
namespace: dq-slo
port: 8080
tools:
- name: execute
description: Data Quality SLO Check — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: dq-slo.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: dq-slo
baseUri: https://penske.internal.example.com/dq-slo/v1
authentication:
type: bearer
token: $secrets.dq_slo_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Datadog Alert Fatigue Audit — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Datadog Alert Fatigue Audit
description: Datadog Alert Fatigue Audit — contextualized for Penske based on its actual service and tool footprint.
tags:
- datadog
- automation
capability:
exposes:
- type: mcp
namespace: alert-audit
port: 8080
tools:
- name: execute
description: Datadog Alert Fatigue Audit — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: alert-audit.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: alert-audit
baseUri: https://penske.internal.example.com/alert-audit/v1
authentication:
type: bearer
token: $secrets.alert_audit_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Email Phishing Training Campaign Dispatch — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Email Phishing Training Campaign Dispatch
description: Email Phishing Training Campaign Dispatch — contextualized for Penske based on its actual service and tool footprint.
tags:
- enterprise
- automation
capability:
exposes:
- type: mcp
namespace: phish-train
port: 8080
tools:
- name: execute
description: Email Phishing Training Campaign Dispatch — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: phish-train.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: phish-train
baseUri: https://penske.internal.example.com/phish-train/v1
authentication:
type: bearer
token: $secrets.phish_train_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Employee Offboarding Revocation — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Employee Offboarding Revocation
description: Employee Offboarding Revocation — contextualized for Penske based on its actual service and tool footprint.
tags:
- workday
- automation
capability:
exposes:
- type: mcp
namespace: offboarding
port: 8080
tools:
- name: execute
description: Employee Offboarding Revocation — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: offboarding.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: offboarding
baseUri: https://penske.internal.example.com/offboarding/v1
authentication:
type: bearer
token: $secrets.offboarding_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Employee Onboarding Orchestration — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Employee Onboarding Orchestration
description: Employee Onboarding Orchestration — contextualized for Penske based on its actual service and tool footprint.
tags:
- workday
- automation
capability:
exposes:
- type: mcp
namespace: onboarding
port: 8080
tools:
- name: execute
description: Employee Onboarding Orchestration — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: onboarding.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: onboarding
baseUri: https://penske.internal.example.com/onboarding/v1
authentication:
type: bearer
token: $secrets.onboarding_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Enterprise Glossary Term Suggestions — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Enterprise Glossary Term Suggestions
description: Enterprise Glossary Term Suggestions — contextualized for Penske based on its actual service and tool footprint.
tags:
- enterprise
- automation
capability:
exposes:
- type: mcp
namespace: glossary-ai
port: 8080
tools:
- name: execute
description: Enterprise Glossary Term Suggestions — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: glossary-ai.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: glossary-ai
baseUri: https://penske.internal.example.com/glossary-ai/v1
authentication:
type: bearer
token: $secrets.glossary_ai_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Executive KPI Dashboard Nightly Build — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Executive KPI Dashboard Nightly Build
description: Executive KPI Dashboard Nightly Build — contextualized for Penske based on its actual service and tool footprint.
tags:
- power-bi
- automation
capability:
exposes:
- type: mcp
namespace: exec-kpi
port: 8080
tools:
- name: execute
description: Executive KPI Dashboard Nightly Build — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: exec-kpi.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: exec-kpi
baseUri: https://penske.internal.example.com/exec-kpi/v1
authentication:
type: bearer
token: $secrets.exec_kpi_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Expense Report Auto-Approval Under Threshold — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Expense Report Auto-Approval Under Threshold
description: Expense Report Auto-Approval Under Threshold — contextualized for Penske based on its actual service and tool footprint.
tags:
- concur
- automation
capability:
exposes:
- type: mcp
namespace: expense-auto
port: 8080
tools:
- name: execute
description: Expense Report Auto-Approval Under Threshold — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: expense-auto.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: expense-auto
baseUri: https://penske.internal.example.com/expense-auto/v1
authentication:
type: bearer
token: $secrets.expense_auto_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Generate Weekly Executive Technology Digest — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Generate Weekly Executive Technology Digest
description: Generate Weekly Executive Technology Digest — contextualized for Penske based on its actual service and tool footprint.
tags:
- enterprise
- automation
capability:
exposes:
- type: mcp
namespace: exec-digest
port: 8080
tools:
- name: execute
description: Generate Weekly Executive Technology Digest — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: exec-digest.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: exec-digest
baseUri: https://penske.internal.example.com/exec-digest/v1
authentication:
type: bearer
token: $secrets.exec_digest_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
GitHub Copilot License Utilization Report — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: GitHub Copilot License Utilization Report
description: GitHub Copilot License Utilization Report — contextualized for Penske based on its actual service and tool footprint.
tags:
- github
- automation
capability:
exposes:
- type: mcp
namespace: copilot-util
port: 8080
tools:
- name: execute
description: GitHub Copilot License Utilization Report — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: copilot-util.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: copilot-util
baseUri: https://penske.internal.example.com/copilot-util/v1
authentication:
type: bearer
token: $secrets.copilot_util_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
GitHub PR Auto-Label by File Pattern — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: GitHub PR Auto-Label by File Pattern
description: GitHub PR Auto-Label by File Pattern — contextualized for Penske based on its actual service and tool footprint.
tags:
- github
- automation
capability:
exposes:
- type: mcp
namespace: pr-label
port: 8080
tools:
- name: execute
description: GitHub PR Auto-Label by File Pattern — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: pr-label.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: pr-label
baseUri: https://penske.internal.example.com/pr-label/v1
authentication:
type: bearer
token: $secrets.pr_label_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
GitLab Pipeline Failure Triage — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: GitLab Pipeline Failure Triage
description: GitLab Pipeline Failure Triage — contextualized for Penske based on its actual service and tool footprint.
tags:
- gitlab
- automation
capability:
exposes:
- type: mcp
namespace: gl-triage
port: 8080
tools:
- name: execute
description: GitLab Pipeline Failure Triage — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: gl-triage.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: gl-triage
baseUri: https://penske.internal.example.com/gl-triage/v1
authentication:
type: bearer
token: $secrets.gl_triage_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Google Analytics Daily Anomaly Detection — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Google Analytics Daily Anomaly Detection
description: Google Analytics Daily Anomaly Detection — contextualized for Penske based on its actual service and tool footprint.
tags:
- google-analytics
- automation
capability:
exposes:
- type: mcp
namespace: ga-anomaly
port: 8080
tools:
- name: execute
description: Google Analytics Daily Anomaly Detection — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: ga-anomaly.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: ga-anomaly
baseUri: https://penske.internal.example.com/ga-anomaly/v1
authentication:
type: bearer
token: $secrets.ga_anomaly_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Lead Routing Based on Territory — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Lead Routing Based on Territory
description: Lead Routing Based on Territory — contextualized for Penske based on its actual service and tool footprint.
tags:
- salesforce
- automation
capability:
exposes:
- type: mcp
namespace: lead-route
port: 8080
tools:
- name: execute
description: Lead Routing Based on Territory — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: lead-route.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: lead-route
baseUri: https://penske.internal.example.com/lead-route/v1
authentication:
type: bearer
token: $secrets.lead_route_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Learning Path Assignment Based on Role — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Learning Path Assignment Based on Role
description: Learning Path Assignment Based on Role — contextualized for Penske based on its actual service and tool footprint.
tags:
- pluralsight
- automation
capability:
exposes:
- type: mcp
namespace: learning-path
port: 8080
tools:
- name: execute
description: Learning Path Assignment Based on Role — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: learning-path.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: learning-path
baseUri: https://penske.internal.example.com/learning-path/v1
authentication:
type: bearer
token: $secrets.learning_path_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
LinkedIn Company Page Engagement Digest — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: LinkedIn Company Page Engagement Digest
description: LinkedIn Company Page Engagement Digest — contextualized for Penske based on its actual service and tool footprint.
tags:
- linkedin
- automation
capability:
exposes:
- type: mcp
namespace: li-digest
port: 8080
tools:
- name: execute
description: LinkedIn Company Page Engagement Digest — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: li-digest.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: li-digest
baseUri: https://penske.internal.example.com/li-digest/v1
authentication:
type: bearer
token: $secrets.li_digest_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Microsoft Teams Channel Creation for Project — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Microsoft Teams Channel Creation for Project
description: Microsoft Teams Channel Creation for Project — contextualized for Penske based on its actual service and tool footprint.
tags:
- microsoft-teams
- automation
capability:
exposes:
- type: mcp
namespace: teams-create
port: 8080
tools:
- name: execute
description: Microsoft Teams Channel Creation for Project — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: teams-create.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: teams-create
baseUri: https://penske.internal.example.com/teams-create/v1
authentication:
type: bearer
token: $secrets.teams_create_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Month-End Financial Close Orchestration — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Month-End Financial Close Orchestration
description: Month-End Financial Close Orchestration — contextualized for Penske based on its actual service and tool footprint.
tags:
- sap
- automation
capability:
exposes:
- type: mcp
namespace: month-end
port: 8080
tools:
- name: execute
description: Month-End Financial Close Orchestration — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: month-end.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: month-end
baseUri: https://penske.internal.example.com/month-end/v1
authentication:
type: bearer
token: $secrets.month_end_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
New Relic Synthetic Monitoring Refresh — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: New Relic Synthetic Monitoring Refresh
description: New Relic Synthetic Monitoring Refresh — contextualized for Penske based on its actual service and tool footprint.
tags:
- new-relic
- automation
capability:
exposes:
- type: mcp
namespace: nr-synth
port: 8080
tools:
- name: execute
description: New Relic Synthetic Monitoring Refresh — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: nr-synth.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: nr-synth
baseUri: https://penske.internal.example.com/nr-synth/v1
authentication:
type: bearer
token: $secrets.nr_synth_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Open Requisition Funnel Report — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Open Requisition Funnel Report
description: Open Requisition Funnel Report — contextualized for Penske based on its actual service and tool footprint.
tags:
- workday
- automation
capability:
exposes:
- type: mcp
namespace: req-funnel
port: 8080
tools:
- name: execute
description: Open Requisition Funnel Report — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: req-funnel.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: req-funnel
baseUri: https://penske.internal.example.com/req-funnel/v1
authentication:
type: bearer
token: $secrets.req_funnel_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Opportunity Pipeline Health Alert — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Opportunity Pipeline Health Alert
description: Opportunity Pipeline Health Alert — contextualized for Penske based on its actual service and tool footprint.
tags:
- salesforce
- automation
capability:
exposes:
- type: mcp
namespace: pipe-health
port: 8080
tools:
- name: execute
description: Opportunity Pipeline Health Alert — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: pipe-health.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: pipe-health
baseUri: https://penske.internal.example.com/pipe-health/v1
authentication:
type: bearer
token: $secrets.pipe_health_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Oracle Database Free-Space Alert — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Oracle Database Free-Space Alert
description: Oracle Database Free-Space Alert — contextualized for Penske based on its actual service and tool footprint.
tags:
- oracle
- automation
capability:
exposes:
- type: mcp
namespace: db-space
port: 8080
tools:
- name: execute
description: Oracle Database Free-Space Alert — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: db-space.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: db-space
baseUri: https://penske.internal.example.com/db-space/v1
authentication:
type: bearer
token: $secrets.db_space_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
P1 Incident Response Orchestration — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: P1 Incident Response Orchestration
description: P1 Incident Response Orchestration — contextualized for Penske based on its actual service and tool footprint.
tags:
- servicenow
- automation
capability:
exposes:
- type: mcp
namespace: incident
port: 8080
tools:
- name: execute
description: P1 Incident Response Orchestration — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: incident.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: incident
baseUri: https://penske.internal.example.com/incident/v1
authentication:
type: bearer
token: $secrets.incident_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Payroll Headcount Snapshot — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Payroll Headcount Snapshot
description: Payroll Headcount Snapshot — contextualized for Penske based on its actual service and tool footprint.
tags:
- workday
- automation
capability:
exposes:
- type: mcp
namespace: headcount
port: 8080
tools:
- name: execute
description: Payroll Headcount Snapshot — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: headcount.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: headcount
baseUri: https://penske.internal.example.com/headcount/v1
authentication:
type: bearer
token: $secrets.headcount_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
PeopleSoft HR Data Sync — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: PeopleSoft HR Data Sync
description: PeopleSoft HR Data Sync — contextualized for Penske based on its actual service and tool footprint.
tags:
- peoplesoft
- automation
capability:
exposes:
- type: mcp
namespace: ps-sync
port: 8080
tools:
- name: execute
description: PeopleSoft HR Data Sync — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: ps-sync.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: ps-sync
baseUri: https://penske.internal.example.com/ps-sync/v1
authentication:
type: bearer
token: $secrets.ps_sync_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Power BI Dataset Refresh Failure Triage — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Power BI Dataset Refresh Failure Triage
description: Power BI Dataset Refresh Failure Triage — contextualized for Penske based on its actual service and tool footprint.
tags:
- power-bi
- automation
capability:
exposes:
- type: mcp
namespace: pbi-triage
port: 8080
tools:
- name: execute
description: Power BI Dataset Refresh Failure Triage — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: pbi-triage.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: pbi-triage
baseUri: https://penske.internal.example.com/pbi-triage/v1
authentication:
type: bearer
token: $secrets.pbi_triage_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Proactive Churn Outreach from Model — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Proactive Churn Outreach from Model
description: Proactive Churn Outreach from Model — contextualized for Penske based on its actual service and tool footprint.
tags:
- snowflake
- automation
capability:
exposes:
- type: mcp
namespace: churn-out
port: 8080
tools:
- name: execute
description: Proactive Churn Outreach from Model — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: churn-out.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: churn-out
baseUri: https://penske.internal.example.com/churn-out/v1
authentication:
type: bearer
token: $secrets.churn_out_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Production Hotfix Change Ticket Automation — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Production Hotfix Change Ticket Automation
description: Production Hotfix Change Ticket Automation — contextualized for Penske based on its actual service and tool footprint.
tags:
- github
- automation
capability:
exposes:
- type: mcp
namespace: hotfix
port: 8080
tools:
- name: execute
description: Production Hotfix Change Ticket Automation — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: hotfix.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: hotfix
baseUri: https://penske.internal.example.com/hotfix/v1
authentication:
type: bearer
token: $secrets.hotfix_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Risk Register Nightly Sync — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Risk Register Nightly Sync
description: Risk Register Nightly Sync — contextualized for Penske based on its actual service and tool footprint.
tags:
- enterprise
- automation
capability:
exposes:
- type: mcp
namespace: risk-register
port: 8080
tools:
- name: execute
description: Risk Register Nightly Sync — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: risk-register.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: risk-register
baseUri: https://penske.internal.example.com/risk-register/v1
authentication:
type: bearer
token: $secrets.risk_register_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Role Change Approval — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Role Change Approval
description: Role Change Approval — contextualized for Penske based on its actual service and tool footprint.
tags:
- workday
- automation
capability:
exposes:
- type: mcp
namespace: role-change
port: 8080
tools:
- name: execute
description: Role Change Approval — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: role-change.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: role-change
baseUri: https://penske.internal.example.com/role-change/v1
authentication:
type: bearer
token: $secrets.role_change_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Salesforce Case Escalation — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Salesforce Case Escalation
description: Salesforce Case Escalation — contextualized for Penske based on its actual service and tool footprint.
tags:
- salesforce
- automation
capability:
exposes:
- type: mcp
namespace: case-escalate
port: 8080
tools:
- name: execute
description: Salesforce Case Escalation — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: case-escalate.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: case-escalate
baseUri: https://penske.internal.example.com/case-escalate/v1
authentication:
type: bearer
token: $secrets.case_escalate_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
ServiceNow SLA Breach Prediction — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: ServiceNow SLA Breach Prediction
description: ServiceNow SLA Breach Prediction — contextualized for Penske based on its actual service and tool footprint.
tags:
- servicenow
- automation
capability:
exposes:
- type: mcp
namespace: sla-predict
port: 8080
tools:
- name: execute
description: ServiceNow SLA Breach Prediction — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: sla-predict.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: sla-predict
baseUri: https://penske.internal.example.com/sla-predict/v1
authentication:
type: bearer
token: $secrets.sla_predict_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Snowflake Warehouse Right-Sizing — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Snowflake Warehouse Right-Sizing
description: Snowflake Warehouse Right-Sizing — contextualized for Penske based on its actual service and tool footprint.
tags:
- snowflake
- automation
capability:
exposes:
- type: mcp
namespace: wh-size
port: 8080
tools:
- name: execute
description: Snowflake Warehouse Right-Sizing — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wh-size.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wh-size
baseUri: https://penske.internal.example.com/wh-size/v1
authentication:
type: bearer
token: $secrets.wh_size_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Software Asset Reclaim from Idle Licenses — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Software Asset Reclaim from Idle Licenses
description: Software Asset Reclaim from Idle Licenses — contextualized for Penske based on its actual service and tool footprint.
tags:
- enterprise
- automation
capability:
exposes:
- type: mcp
namespace: asset-reclaim
port: 8080
tools:
- name: execute
description: Software Asset Reclaim from Idle Licenses — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: asset-reclaim.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: asset-reclaim
baseUri: https://penske.internal.example.com/asset-reclaim/v1
authentication:
type: bearer
token: $secrets.asset_reclaim_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Splunk Dashboard Nightly Snapshot — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Splunk Dashboard Nightly Snapshot
description: Splunk Dashboard Nightly Snapshot — contextualized for Penske based on its actual service and tool footprint.
tags:
- splunk
- automation
capability:
exposes:
- type: mcp
namespace: splunk-snap
port: 8080
tools:
- name: execute
description: Splunk Dashboard Nightly Snapshot — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: splunk-snap.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: splunk-snap
baseUri: https://penske.internal.example.com/splunk-snap/v1
authentication:
type: bearer
token: $secrets.splunk_snap_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Splunk Security Event Correlation — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Splunk Security Event Correlation
description: Splunk Security Event Correlation — contextualized for Penske based on its actual service and tool footprint.
tags:
- splunk
- automation
capability:
exposes:
- type: mcp
namespace: splunk-sec
port: 8080
tools:
- name: execute
description: Splunk Security Event Correlation — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: splunk-sec.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: splunk-sec
baseUri: https://penske.internal.example.com/splunk-sec/v1
authentication:
type: bearer
token: $secrets.splunk_sec_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Stale Branch Cleanup — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Stale Branch Cleanup
description: Stale Branch Cleanup — contextualized for Penske based on its actual service and tool footprint.
tags:
- github
- automation
capability:
exposes:
- type: mcp
namespace: branch-cleanup
port: 8080
tools:
- name: execute
description: Stale Branch Cleanup — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: branch-cleanup.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: branch-cleanup
baseUri: https://penske.internal.example.com/branch-cleanup/v1
authentication:
type: bearer
token: $secrets.branch_cleanup_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Tableau Data Source Refresh Orchestration — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Tableau Data Source Refresh Orchestration
description: Tableau Data Source Refresh Orchestration — contextualized for Penske based on its actual service and tool footprint.
tags:
- tableau
- automation
capability:
exposes:
- type: mcp
namespace: tableau-refresh
port: 8080
tools:
- name: execute
description: Tableau Data Source Refresh Orchestration — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: tableau-refresh.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: tableau-refresh
baseUri: https://penske.internal.example.com/tableau-refresh/v1
authentication:
type: bearer
token: $secrets.tableau_refresh_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Tableau Workbook Usage Audit — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Tableau Workbook Usage Audit
description: Tableau Workbook Usage Audit — contextualized for Penske based on its actual service and tool footprint.
tags:
- tableau
- automation
capability:
exposes:
- type: mcp
namespace: tableau-audit
port: 8080
tools:
- name: execute
description: Tableau Workbook Usage Audit — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: tableau-audit.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: tableau-audit
baseUri: https://penske.internal.example.com/tableau-audit/v1
authentication:
type: bearer
token: $secrets.tableau_audit_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Unified Customer Lookup Across Systems — contextualized for Penske based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Unified Customer Lookup Across Systems
description: Unified Customer Lookup Across Systems — contextualized for Penske based on its actual service and tool footprint.
tags:
- salesforce
- automation
capability:
exposes:
- type: mcp
namespace: customer-lookup
port: 8080
tools:
- name: execute
description: Unified Customer Lookup Across Systems — contextualized for Penske based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: customer-lookup.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: customer-lookup
baseUri: https://penske.internal.example.com/customer-lookup/v1
authentication:
type: bearer
token: $secrets.customer_lookup_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: api-developer
info:
label: Penske API Source Capability
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
tags:
- naftiko
- source-capability
- api
- role:api-developer
capability:
exposes:
- type: mcp
namespace: penske-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-api
baseUri: https://api.penske.example.com/v1
authentication:
type: bearer
token: $secrets.penske_api_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: backend-developer
info:
label: Penske API Source Capability
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
tags:
- naftiko
- source-capability
- api
- role:backend-developer
capability:
exposes:
- type: mcp
namespace: penske-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-api
baseUri: https://api.penske.example.com/v1
authentication:
type: bearer
token: $secrets.penske_api_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Applied capability exposing governance metadata, policy compliance, and audit trails for Penske's capability fabric.
naftiko: '0.5'
naftiko_role_recommendation: chief-information-officer
info:
label: Penske Governance Capability
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Penske's capability fabric.
tags:
- naftiko
- applied-capability
- governance
- role:chief-information-officer
capability:
exposes:
- type: mcp
namespace: penske-governance
port: 8080
tools:
- name: execute
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Penske's capability fabric.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-governance.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-governance
baseUri: https://governance.penske.example.com/v1
authentication:
type: bearer
token: $secrets.penske_governance_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
naftiko: '0.5'
naftiko_role_recommendation: cloud-architect
info:
label: Penske Operations Capability
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
tags:
- naftiko
- applied-capability
- observability
- role:cloud-architect
capability:
exposes:
- type: mcp
namespace: penske-ops
port: 8080
tools:
- name: execute
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-ops.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-ops
baseUri: https://ops.penske.example.com/fabric/v1
authentication:
type: bearer
token: $secrets.penske_ops_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
naftiko: '0.5'
naftiko_role_recommendation: cloud-engineer
info:
label: Penske Operations Capability
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
tags:
- naftiko
- applied-capability
- observability
- role:cloud-engineer
capability:
exposes:
- type: mcp
namespace: penske-ops
port: 8080
tools:
- name: execute
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-ops.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-ops
baseUri: https://ops.penske.example.com/fabric/v1
authentication:
type: bearer
token: $secrets.penske_ops_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Applied capability exposing governance metadata, policy compliance, and audit trails for Penske's capability fabric.
naftiko: '0.5'
naftiko_role_recommendation: cloud-security-engineer
info:
label: Penske Governance Capability
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Penske's capability fabric.
tags:
- naftiko
- applied-capability
- governance
- role:cloud-security-engineer
capability:
exposes:
- type: mcp
namespace: penske-governance
port: 8080
tools:
- name: execute
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Penske's capability fabric.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-governance.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-governance
baseUri: https://governance.penske.example.com/v1
authentication:
type: bearer
token: $secrets.penske_governance_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability that orchestrates Penske's data sources into a single MCP-ready pipeline for analytics and AI workloads.
naftiko: '0.5'
naftiko_role_recommendation: data-engineer
info:
label: Penske Data Pipeline Capability
description: Naftiko applied capability that orchestrates Penske's data sources into a single MCP-ready pipeline for analytics and AI workloads.
tags:
- naftiko
- applied-capability
- data
- role:data-engineer
capability:
exposes:
- type: mcp
namespace: penske-data
port: 8080
tools:
- name: execute
description: Naftiko applied capability that orchestrates Penske's data sources into a single MCP-ready pipeline for analytics and AI workloads.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-data.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-data
baseUri: https://data.penske.example.com/pipelines/v1
authentication:
type: bearer
token: $secrets.penske_data_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
naftiko: '0.5'
naftiko_role_recommendation: director-of-cloud-engineering
info:
label: Penske Operations Capability
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
tags:
- naftiko
- applied-capability
- observability
- role:director-of-cloud-engineering
capability:
exposes:
- type: mcp
namespace: penske-ops
port: 8080
tools:
- name: execute
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Penske's SREs and operators.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-ops.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-ops
baseUri: https://ops.penske.example.com/fabric/v1
authentication:
type: bearer
token: $secrets.penske_ops_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: director-of-engineering
info:
label: Penske Platform Catalog Capability
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:director-of-engineering
capability:
exposes:
- type: mcp
namespace: penske-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-platform
baseUri: https://backstage.penske.example.com/api/catalog
authentication:
type: bearer
token: $secrets.penske_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: director-of-platform-engineering
info:
label: Penske Platform Catalog Capability
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:director-of-platform-engineering
capability:
exposes:
- type: mcp
namespace: penske-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-platform
baseUri: https://backstage.penske.example.com/api/catalog
authentication:
type: bearer
token: $secrets.penske_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: full-stack-developer
info:
label: Penske API Source Capability
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
tags:
- naftiko
- source-capability
- api
- role:full-stack-developer
capability:
exposes:
- type: mcp
namespace: penske-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-api
baseUri: https://api.penske.example.com/v1
authentication:
type: bearer
token: $secrets.penske_api_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: head-of-api
info:
label: Penske API Source Capability
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
tags:
- naftiko
- source-capability
- api
- role:head-of-api
capability:
exposes:
- type: mcp
namespace: penske-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Penske's primary API surface, exposing it via MCP and REST for downstream reuse.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-api
baseUri: https://api.penske.example.com/v1
authentication:
type: bearer
token: $secrets.penske_api_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: head-of-integration
info:
label: Penske MCP Context Tool
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
tags:
- naftiko
- applied-capability
- mcp
- role:head-of-integration
capability:
exposes:
- type: mcp
namespace: penske-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-context
baseUri: https://internal.penske.example.com/context/v1
authentication:
type: bearer
token: $secrets.penske_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: head-of-platform-engineering
info:
label: Penske Platform Catalog Capability
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:head-of-platform-engineering
capability:
exposes:
- type: mcp
namespace: penske-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-platform
baseUri: https://backstage.penske.example.com/api/catalog
authentication:
type: bearer
token: $secrets.penske_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: integration-architect
info:
label: Penske MCP Context Tool
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
tags:
- naftiko
- applied-capability
- mcp
- role:integration-architect
capability:
exposes:
- type: mcp
namespace: penske-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-context
baseUri: https://internal.penske.example.com/context/v1
authentication:
type: bearer
token: $secrets.penske_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: mlops-engineer
info:
label: Penske MCP Context Tool
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
tags:
- naftiko
- applied-capability
- mcp
- role:mlops-engineer
capability:
exposes:
- type: mcp
namespace: penske-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-context
baseUri: https://internal.penske.example.com/context/v1
authentication:
type: bearer
token: $secrets.penske_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: platform-engineer
info:
label: Penske Platform Catalog Capability
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:platform-engineer
capability:
exposes:
- type: mcp
namespace: penske-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-platform
baseUri: https://backstage.penske.example.com/api/catalog
authentication:
type: bearer
token: $secrets.penske_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: prompt-engineer
info:
label: Penske MCP Context Tool
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
tags:
- naftiko
- applied-capability
- mcp
- role:prompt-engineer
capability:
exposes:
- type: mcp
namespace: penske-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-context
baseUri: https://internal.penske.example.com/context/v1
authentication:
type: bearer
token: $secrets.penske_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: solutions-architect
info:
label: Penske MCP Context Tool
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
tags:
- naftiko
- applied-capability
- mcp
- role:solutions-architect
capability:
exposes:
- type: mcp
namespace: penske-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-context
baseUri: https://internal.penske.example.com/context/v1
authentication:
type: bearer
token: $secrets.penske_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: technical-lead
info:
label: Penske MCP Context Tool
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
tags:
- naftiko
- applied-capability
- mcp
- role:technical-lead
capability:
exposes:
- type: mcp
namespace: penske-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Penske's existing source APIs, exposed as an MCP tool for agent context engineering.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-context
baseUri: https://internal.penske.example.com/context/v1
authentication:
type: bearer
token: $secrets.penske_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: vp-of-engineering
info:
label: Penske Platform Catalog Capability
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:vp-of-engineering
capability:
exposes:
- type: mcp
namespace: penske-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Penske's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: penske-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: penske-platform
baseUri: https://backstage.penske.example.com/api/catalog
authentication:
type: bearer
token: $secrets.penske_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Score Breakdown — Total: 651
Each row links to its full definition on the Naftiko Signal Groups page.
12 8 2 22 29 13 22 20 8 65 12 15 40 6 8 10 12 12 2 23 19 22 10 8 39 57 14 6 14 2 2 0 8 6 28 11 11 3 6 21 23Areas — Total: 568
- AI Applications
- AI Governance
- AI Platforms
- AI Solutions
- AI Technologies
- AI Tools
- API Gateways
- API Management
- Acceptance Testing
- Access Controls
- Access Management
- Accountability
- Accounting
- Administration
- Administratives
- Advertising
- Agentic AI
- Agentic Solutions
- Agentics
- Alerting
- Alerts
- Algorithms
- Analysis
- Androids
- Applicant Tracking Systems
- Application Architectures
- Application Development
- Application Lifecycle Management
- Application Programming Interfaces
- Application Servers
- Applications
- Architectures
- Archives
- Artificial Intelligence
- Artificial Intelligence/Machine Learning
- Assessments
- Asset Management
- Asset Managers
- Assignments
- Audits
- Australias
- Authentications
- Authorizations
- Automated Testing
- Automation
- Automotive
- Awareness
- BI
- Background Checks
- Backups
- Bashes
- Battery Technologies
- Benchmarkings
- Benchmarks
- Best Practices
- Big Data
- Billings
- Bridges
- Business
- Business Analytics
- Business Continuities
- Business Models
- Business Operations
- Business Plannings
- Business Plans
- Business Process
- Business Process Automation
- Business Software
- Business Strategies
- Business to Consumers
- Business-to-Business
- C
- CI
- Cameras
- Career Development
- Certificates
- Certifications
- Charting
- Charts
- Chats
- Cities
- Clients
- Climates
- Cloud Architectures
- Cloud Computing
- Cloud Computing Platforms
- Cloud Connectivity
- Cloud Data
- Cloud Data Platforms
- Cloud Database Technologies
- Cloud Databases
- Cloud Engineering
- Cloud Environments
- Cloud Infrastructure
- Cloud Networking
- Cloud Platforms
- Cloud Systems
- Cloud-Based
- Clouds
- Code Management
- Code Quality
- Code Reviews
- Collaborations
- Collections
- Communications
- Communities
- Compliance
- Computer Sciences
- Computer Systems
- Computer Visions
- Computers
- Computes
- Computing
- Configurations
- Connectivity
- Connectors
- Consultings
- Contacts
- Container Orchestration
- Containerization
- Containerization Technologies
- Containers
- Continuous Deliveries
- Continuous Improvements
- Continuous Integration/Continuous Deployments
- Contributions
- Controls
- Coordinates
- Cost Accounting
- Cost Management
- Critical Thinkings
- Customer Analytics
- Customer Data
- Customer Data Platforms
- Customer Experiences
- Customer Feedback
- Customer Relationship Management
- Customer Satisfactions
- Customer Service
- Customer Support
- Dashboards
- Data Access
- Data Analysis
- Data Analytics
- Data Analytics Tools
- Data Architectures
- Data Centers
- Data Collections
- Data Distributions
- Data Engineering
- Data Entries
- Data Extractions
- Data Flows
- Data Gatherings
- Data Governance
- Data Ingestions
- Data Integrations
- Data Integrity
- Data Lakes
- Data Management
- Data Mining
- Data Pipelines
- Data Platforms
- Data Preparations
- Data Processing
- Data Quality
- Data Sciences
- Data Securities
- Data Storage
- Data Strategies
- Data Structures
- Data Tools
- Data Transformations
- Data Visualizations
- Data Warehouses
- Data Warehousing
- Data and Analytics
- Data-Driven
- Database Management
- Database Technologies
- Databases
- Decentralized
- Decision Making
- Deliveries
- Dependencies
- Deployment Strategies
- Deployments
- Design Tools
- Desktops
- DevOps Practices
- Development Lifecycle
- Development Process
- Diagnostics
- Digital Experiences
- Digital Products
- Digital Systems
- Digital Technologies
- Digital Transformations
- Digitals
- Directory
- Disaster Recovery
- Distributed
- Distributed Systems
- Distributions
- Document Management
- Documentations
- Documents
- Due Diligences
- Dynamics
- E-mails
- Earth Sciences
- Economics
- Educations
- Efficiencies
- Electronic Data Interchange
- Electronics
- Emails
- Employee Engagements
- Employment
- Enablement
- End To End
- Energies
- Energy Infrastructure
- Engineering
- Enterprise Applications
- Enterprise Data
- Enterprise IT
- Enterprises
- Equipments
- Ethics
- Evaluations
- Events
- Excels
- Executions
- Extensions
- Extract Transform Loads
- Federations
- Feedback
- Finances
- Financial Analysis
- Financial Data
- Financial Management
- Financial Models
- Financial Plannings
- Financial Policies
- Financial Reportings
- Firewalls
- Flexibilities
- Forecasting
- Forms
- Foundations
- Frameworks
- Freight Forwardings
- Functions
- Gateways
- General Ledgers
- Generative AI
- Geographies
- Goal Settings
- Governance
- Governance Frameworks
- Government
- HCM
- HR Technologies
- Heating, Ventilation, and Air Conditionings
- High Availabilities
- Hirings
- Human Resources
- Hybrid Clouds
- IT Infrastructure
- IT Project Management
- Ideas
- Identities
- Identity And Access Management
- Identity Management
- Implementations
- Incident Management
- Incident Responses
- Industrial Engineering
- Information Systems
- Information Technologies
- Infrastructure
- Infrastructure As Codes
- Innovation
- Insights
- Inspections
- Insurances
- Integration Workflows
- Integrations
- Integrity
- Intelligence
- Interactives
- Interfaces
- Internal Controls
- Internet
- Inventory Management
- Investments
- Key Metrics
- Knowledge Sharing
- Large Datasets
- Leaderships
- Learning
- Ledgers
- Legal
- Libraries
- Licensings
- Lifecycle Management
- Load Balancers
- Logging
- Logistics
- Machine Learning
- Machine Learning Algorithms
- Machine Learning Models
- Machine Learning Platforms
- Mails
- Maintenance
- Managed Services
- Management
- Management Information
- Management Software
- Management Systems
- Management Tools
- Manual Processes
- Manufacturing
- Mappings
- Market Researches
- Marketing
- Markets
- Mathematics
- Measurements
- Media
- Meetings
- Mentoring
- Message Queuings
- Messaging
- Metadata
- Metrics
- Micro-services
- Microservices
- Microsoft Access
- Middlewares
- Migrations
- Mobile Apps
- Mobiles
- Model Deployments
- Modeling
- Monitoring
- Multiple Systems
- Navigation
- Negotiations
- Network Architectures
- Network Design
- Network Engineering
- Networking
- News
- NoSQL
- Notifications
- Observability
- Observability Tools
- Office Suites
- Onboardings
- Open Source
- Operating Systems
- Operational Efficiencies
- Operational Excellence
- Operational Technologies
- Operations Management
- Operations Researches
- Operators
- Optimizations
- Options
- Orchestration
- Organizations
- Packages
- Patterns
- Payments
- Payroll
- Performance
- Performance Management
- Performance Metrics
- Performance Testing
- Pipelines
- Pivot Tables
- Plannings
- Platform Engineering
- Platforms
- Policies
- Portals
- Power Tools
- Predictive Analytics
- Presentations
- Pricing Models
- Pricing Strategies
- Pricings
- Prioritizations
- Problem Solving
- Process Analytics
- Process Automation
- Process Controls
- Process Design
- Process Documentations
- Process Improvements
- Process Mappings
- Processes
- Procurements
- Product Development
- Product Management
- Product Owners
- Product Platforms
- Product Strategies
- Production
- Production Support
- Productivity
- Products
- Professional Trainings
- Program Management
- Programming
- Project Management
- Project Schedules
- Projects
- Protection
- Proxies
- Purchasings
- QA
- Quality Controls
- Quantitative Modeling
- Ratings
- Real Estates
- Real Time
- Real-time Data
- Real-time Insights
- Real-time Visibility
- Reasonings
- Reconciliations
- Record Keepings
- Recordings
- Recruitings
- Recruitment
- Registrations
- Relationals
- Relationship Buildings
- Relationship Management
- Release Management
- Reliabilities
- Renewable Energies
- Reporting Systems
- Reportings
- Requirements
- Research
- Resiliences
- Resiliency
- Resilient Systems
- Retails
- Revenues
- Reviews
- Risk Assessments
- Root Cause Analysis
- Routings
- SQL Databases
- SQL Queries
- SaaS Solutions
- Safes
- Safety
- Sales
- Scalabilities
- Scaling
- Scheduling
- Scorings
- Screenings
- Scriptings
- Security Best Practices
- Security Requirements
- Sensors
- Servers
- Service Desks
- Service Meshes
- Service Operations
- Settlements
- Shippings
- Simulations
- Social
- Social Media
- Software
- Software Configuration Management
- Software Development
- Software Engineering
- Software Quality
- Software Solutions
- Software Tools
- Solutions
- Source Code Management
- Source Codes
- Sourcings
- Stakeholder Management
- Startups
- Statistical Analysis
- Statistical Modeling
- Statistics
- Storage
- Strategic Design
- Strategies
- Stream Processing
- Supplier Management
- Supply Chains
- Sustainability
- Switches
- System Architectures
- System Design
- System Development
- System Enhancements
- System Maintenance
- System Performances
- System Requirements
- System Solutions
- Systems
- Systems Architectures
- Systems Development
- Systems Engineering
- Systems Thinkings
- Talent Acquisition
- Talent Management
- Tasks
- Taxes
- Technical Support
- Technologies
- Technology Platforms
- Technology Stacks
- Technology Strategies
- Test Instruments
- Test Strategies
- Testing Frameworks
- Testing Strategies
- Testing Tools
- Tickets
- Time Management
- Timelines
- Total Rewards
- Tracking
- Transformations
- Transparency
- Transportation
- Travels
- Troubleshooting
- UI
- UX
- Underwritings
- Unstructured Data
- Updates
- Uptime
- User Lifecycle
- Validation
- Vehicle Repairs
- Verifications
- Videos
- Visibility
- Visualizations
- Voice
- Warehouse Automation
- Warehouse Equipments
- Warehouse Management
- Web Based
- Webinars
- Webs
- Words
- Workflows
- Workforce Development
- Workshops
- Workspaces
Services — Total: 57
- Adobe Launch
- Alteryx
- Amazon Web Services
- Apple
- Azure Active Directory
- Box
- CloudFormation
- Datadog
- Dynatrace
- Google Analytics
- Google Apps Script
- Google Campaign Manager
- Google Cloud Platform
- Google Drive
- Google Maps
- Google Sheets
- Harness
- Make
- Microsoft
- Microsoft 365
- Microsoft Azure
- Microsoft Edge
- Microsoft Entra
- Microsoft Exchange
- Microsoft Graph
- Microsoft Office
- Microsoft Outlook
- Microsoft Planner
- Microsoft Power Automate
- Microsoft PowerPoint
- Microsoft Project
- Microsoft Teams
- Microsoft Visio
- OpenShift
- Oracle
- Oracle Enterprise Manager
- Power BI
- Power Query
- Qlik
- Qlik Sense
- QlikView
- SAP
- SAP BI
- SQL Server
- SharePoint
- Shopify
- Snowflake
- Solaris Zones
- Splunk
- Spot
- Square
- Tableau Desktop
- Talend
- WebSphere
- Youtube
Tools — Total: 29
- Angular
- Apache AGE
- Apache Airflow
- Apache Flex
- Apache JMeter
- Apache Kafka
- Apache Phoenix
- Apache Pivot
- Apache Spark
- Apache Streams
- Buildpacks
- Cucumber
- Docker
- Elk Stack
- Grafana
- Helm
- Kubernetes
- Lean
- Linux
- Packer
- PowerShell
- Prometheus
- Python
- R
- React
- Score
- Selenium
- Spring Framework
- Terraform
Standards — Total: 47
- Acceptance Criteria
- Agile Methodology
- CODE_OF_CONDUCT.md
- CONTRIBUTORS.md
- CS
- Certificate Enrolment Protocols
- DNS
- DOT Regulations
- Data Modeling
- Data Models
- DevOps
- DevSecOps
- Enterprise Integration Patterns
- GDPR
- HTML
- HTTP
- IAM
- ISO
- LICENSE.md
- Lean Operations
- Lean Six Sigma Black Belt
- MLOps
- Methodology
- OAuth
- OSHA
- OpenID Connect
- PCI Compliance
- Process Flow Diagrams
- Quality Standards
- RBAC
- REST
- Regulation
- Regulatory
- SAML
- SQL
- SSO
- Six Sigma
- Software Design Patterns
- Software-Defined Networking
- Specification
- Standard Operating Procedures
- Standardization
- Standards
- TCP/IP
- Templates
- XML
- Zero Trust Architecture
Why do we do this?
- Understand the state of the market.
- Meet new and diverse design partners.
- Help us prioritize business capabilities.
Who is this for?
- AI, API, integration and platform leadership.
- The C-Suite looking to navigate their enterprises.
- Analysts and media outlets reporting on technology.
Why become a design partner?
- Collaboration to define your business capabilities.
- Obtain more control over the integrations you have.
- Help shape the Naftiko roadmap to meet your needs.
About This Research
- Signals summarize how we rate overall investments made.
- Areas reveal the technology areas being invested in.
- Services show which services are part their SaaS portfolio.
- Tools highlight the open-source investments being made.
- Standards speak to how aligned integrations are with market.
About This Guidance
- Impact Report outlines the data behind their AI response.
- Impact Summary provides the narrative for their AI response.
- Radar looks at the maturity of the investments being made.
- Capabilities are how Naftiko can help strengthen capabilities.
- Navigation provides handful of areas to consider more investment.