Wells Fargo Signals
One of the largest banks in the United States providing banking, investment, mortgage, and consumer and commercial finance services. Serves one in three American households and more than 10% of small businesses in the country.
This is a Naftiko Signals read of Wells Fargo’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 Wells Fargo we detected 1103 areas, 212 services, 152 tools, and 159 standards — producing a total signal score of 1656.
How to read this page: Impact Report is the narrative read-out. Capabilities are Naftiko agent workflows you could ship on top of Wells Fargo’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.
Wells Fargo Technology Investment Impact Report
| Prepared by Naftiko | April 2026 |
Executive Summary
This report presents a signal-based analysis of Wells Fargo’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.
One of the largest banks in the United States providing banking, investment, mortgage, and consumer and commercial finance services. Serves one in three American households and more than 10% of small businesses in the country.
The assessment yields a total signal score of 1656 across 41 dimensions. The six strongest signal categories are services (212), data (129), cloud (126), automation (86), operations (86), security (82).
Layer 1: Foundational Layer
Evaluating Wells Fargo’s foundational capabilities across Artificial Intelligence, Cloud, Open-Source, Languages, and Code — the core infrastructure and development building blocks supporting Financial Technology / Payment Processing and Financial Services / Banking operations.
Waves: Large Language Models (LLMs), Generative Pre-trained Transformer (GPT), Open-Source LLMs
Artificial Intelligence — Score: 67 #17/106
Wells Fargo’s AI score of 67 reflects adoption across Azure Machine Learning, Bloomberg AIM, Databricks.
- Services: Azure Machine Learning, Bloomberg AIM, Databricks, GitHub Copilot, Hugging Face, Microsoft Copilot, OpenAI
- Tools: Hugging Face Transformers, Kubeflow, Matplotlib, NumPy, Pandas, PyTorch, Semantic Kernel, TensorFlow
- Concepts: AI Agents, Agent Frameworks, Agentic AI, Agentic Frameworks, Agentic Solutions, Agentic Systems, Agentics, Agents
- Standards: MLOps
AI posture sets the ceiling on downstream AI workloads at Wells Fargo.
Cloud — Score: 126 #3/106
Cloud score of 126 spans Amazon API Gateway, Amazon ECS, Amazon Kinesis alongside IaC tooling (Ansible, Buildpacks, Docker).
- Services: Amazon API Gateway, Amazon ECS, Amazon Kinesis, Amazon S3, Amazon SNS, Amazon Web Services, Azure Active Directory, Azure Data Factory
- Tools: Ansible, Buildpacks, Docker, Kubernetes, Terraform
- Concepts: Cloud Adoptions, Cloud Architectures, Cloud Computing, Cloud Data, Cloud Data Platforms, Cloud Databases, Cloud Ecosystems, Cloud Engineering
- Standards: SDLC, Software Development Lifecycle
Cloud maturity is the anchor for scaling AI workloads at Wells Fargo.
Open-Source — Score: 42 #2/106
Open-Source score of 42 anchored on Bitbucket, GitHub, GitHub Copilot.
- Services: Bitbucket, GitHub, GitHub Copilot, GitLab, Red Hat
- Tools: Angular, Ansible, Ansible Playbooks, Apache, Apache AGE, Apache Airflow, Apache Ant, Apache Archiva
- Concepts: Contributions, Open-source Programming Languages
- Standards: CONTRIBUTING.md, CONTRIBUTORS.md, LICENSE.md, SECURITY.md, SUPPORT.md
Consumption is broad; formal contribution posture is an opportunity area.
Languages — Score: 37 #16/106
Languages score of 37 across .Net, .Net Core, Bash, C#, C++.
- Languages: .Net, .Net Core, Bash, C#, C++, C++17, C++20, Gherkin
Language mix is a revealing signal of Wells Fargo’s engineering history and modernization priorities.
Code — Score: 51 #32/106
Code score of 51 anchored on Azure DevOps, Bitbucket, GitHub.
- Services: Azure DevOps, Bitbucket, GitHub, GitHub Actions, GitHub Copilot, GitLab, IntelliJ IDEA, TeamCity
- Tools: Git, PowerShell, SonarQube, Vitess
- Concepts: Application Programming Interfaces, Code Coverages, Code Quality, Code Reviews, Codes, Continuous Integration/Continuous Deployments, Continuous Integrations, Developer Experiences
- Standards: DevOps, SDLC, Secure Software Development Lifecycle, Software Development Lifecycle
Developer tooling is the lever for compound productivity via AI coding assistants.
Layer Summary: Wells Fargo’s Foundational Layer reflects AI (67), Cloud (126), Open-Source (42), Languages (37), and Code (51) — the bedrock on which every subsequent AI-readiness capability is built.
Layer 2: Retrieval & Grounding
Evaluating Wells Fargo’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: 129 #14/106
Data score of 129 reflects Alteryx, Azure Data Factory, Crystal Reports.
- Services: Alteryx, Azure Data Factory, Crystal Reports, Databricks, Power BI, Power Query, QlikSense, Snowflake
- Tools: Apache Airflow, Apache Hadoop, Apache Hive, Apache Iceberg, Apache Kafka, Apache NiFi, Apache Spark, ClickHouse
- Concepts: Analytics, Business Analytics, Business Intelligence, Data Analysis, Data Analysis Tools, Data Analytics, Data Analytics Platforms, Data Analytics Tools
- Standards: Data Modeling, Data Models
Analytical depth is the foundation for retrieval-augmented AI.
Databases — Score: 34 #6/106
Databases score of 34 spans Oracle, Oracle Cloud, Snowflake.
- Services: Oracle, Oracle Cloud, Snowflake, Teradata
- Tools: ClickHouse, Elasticsearch, MongoDB, MySQL, PostgreSQL, Redis
- Concepts: Cloud Databases, Database Design, Database Queries, Database Technologies, Databases, In-Memory Databases, NoSQL, Relational Data
- Standards: SQL
Portfolio rationalization is an ongoing lever.
Virtualization — Score: 20 #16/106
Virtualization score of 20 on Citrix NetScaler, Solaris Zones, VMware.
- Services: Citrix NetScaler, Solaris Zones, VMware
- Tools: Docker, Kubernetes
- Concepts: Container Orchestration, Containerization, Containerization Technologies, Containerized Deployments, Containers, Virtualizations
Containerization paired with VMs is a pragmatic stance.
Specifications — Score: 10 #25/106
Specifications score of 10 rooted in REST/HTTP/JSON.
- Concepts: API Gateways, API Securities, Application Programming Interfaces, Capital Markets, Venture Capital, Web API, Web Services, Working Capital
- Standards: HTTP, HTTP/2, JSON, OpenAPI, Protocol Buffers, REST, TCP/IP, WebSockets
Formalizing OpenAPI as enterprise standard is a prerequisite for AI agent integration.
Context Engineering
Wells Fargo’s Context Engineering investment is emerging.
Pairing strong Data with formal context layer is the highest-leverage AI readiness move.
Layer Summary: Wells Fargo’s Retrieval posture is shaped by Data (129), Databases (34), and Specifications (10).
Layer 3: Customization & Adaptation
Evaluating Wells Fargo’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: 15 #32/106
Data Pipelines score of 15 reflects Apache Airflow, Apache DolphinScheduler, Apache Flink.
- Services: Azure Data Factory
- Tools: Apache Airflow, Apache DolphinScheduler, Apache Flink, Apache Hop, Apache Kafka, Apache NiFi, Apache Spark
- Concepts: Cloud Integrations, Continuous Integration/Continuous Deployments, Continuous Integrations, Data Integrations, Data Pipelines, Extract Transform Loads, Integration Testing, Integration Tests
Streaming pipelines prerequisite for real-time AI inference.
Model Registry & Versioning — Score: 15 #27/106
Model Registry score of 15 via Azure Machine Learning, Databricks, Kubeflow.
- Services: Azure Machine Learning, Databricks
- Tools: Kubeflow, PyTorch, TensorFlow
- Standards: MLOps
Enterprise registry with approvals is prerequisite for regulated AI.
Multimodal Infrastructure — Score: 12 #13/106
Multimodal score of 12 via Azure Machine Learning, Hugging Face, OpenAI.
- Services: Azure Machine Learning, Hugging Face, OpenAI
- Tools: PyTorch, Semantic Kernel, TensorFlow
- Concepts: Generative AI, Large Language Models, Multimodals
Centralized OCR/audio/image extractors improve AI project productivity.
Domain Specialization — Score: 2
Domain Specialization score of 2.
Industry-specific fine-tuning is a differentiated long-term capability for Wells Fargo.
Layer Summary: Customization bridges generic AI and business-specific advantage.
Layer 4: Efficiency & Specialization
Evaluating Wells Fargo’s operational efficiency and platform layer — Automation, Containers, Platform, Operations.
Waves: Small Language Models (SLMs), Model Routing / Orchestration, Reasoning Models
Automation — Score: 86 #4/106
Automation score of 86 reflects Ansible Automation Platform, GitHub Actions, Make.
- Services: Ansible Automation Platform, GitHub Actions, Make, Microsoft Power Apps, Microsoft Power Automate, Power Apps, Red Hat Ansible Automation Platform, ServiceNow
- Tools: Ansible, Apache Airflow, PowerShell
- Concepts: Automation, Automation Testing, Build Automation, Building Automation, Deployment Automation, Network Automation, Process Automation, Robotic Process Automation
Automation footprint is ready for AI augmentation on high-toil processes.
Containers — Score: 31 #3/106
Containers score of 31 on Buildpacks, Docker, Helm.
- Tools: Buildpacks, Docker, Helm, Kubernetes
- Concepts: Container Orchestration, Containerization, Containerization Technologies, Containerized Deployments, Containers
Container-native AI deployment is the logical next step.
Platform — Score: 40 #7/106
Platform score of 40 spans Amazon API Gateway, Amazon ECS, Amazon Kinesis.
- Services: Amazon API Gateway, Amazon ECS, Amazon Kinesis, Amazon S3, Amazon SNS, Amazon Web Services, Azure Active Directory, Azure Data Factory
- Concepts: AI Platforms, Banking Platforms, Cloud Data Platforms, Cloud Platforms, Cloud-native Platforms, Cross Platforms, Data Analytics Platforms, Data Platforms
Platform engineering maturity is the next milestone.
Operations — Score: 86 #6/106
Operations score of 86 anchored on Azure Log Analytics, Datadog, Dynatrace.
- Services: Azure Log Analytics, Datadog, Dynatrace, New Relic, ServiceNow, SolarWinds, Splunk
- Tools: Ansible, Prometheus, Puppet, Terraform
- Concepts: Business Operations, Financial Operations, Incident Management, Incident Responses, Operational Excellence, Operations, Operations Management, Security Incident Responses
Operational tooling is a foundation for AI-driven SRE.
Layer Summary: Automation (86) and Operations (86) are direct levers for AI-augmented productivity.
Layer 5: Productivity
Evaluating Wells Fargo’s productivity tooling — SaaS, Services, Code.
Waves: Coding Assistants, Copilots
Software As A Service (SaaS) — Score: 5 #64/106
SaaS score of 5 includes Box, HubSpot, LinkedIn, MailChimp, Microsoft Copilot.
- Services: Box, HubSpot, LinkedIn, MailChimp, Microsoft Copilot, Microsoft Teams, Salesforce, Workday
Rationalization and unified auth are the optimization opportunities.
Code — Score: 51 #32/106
Code anchored on Azure DevOps, Bitbucket, GitHub.
- Services: Azure DevOps, Bitbucket, GitHub, GitHub Actions, GitHub Copilot, GitLab, IntelliJ IDEA, TeamCity
- Tools: Git, PowerShell, SonarQube, Vitess
- Concepts: Application Programming Interfaces, Code Coverages, Code Quality, Code Reviews, Codes, Continuous Integration/Continuous Deployments, Continuous Integrations, Developer Experiences
- Standards: DevOps, SDLC, Secure Software Development Lifecycle, Software Development Lifecycle
Wiring coding assistants creates compound productivity gains.
Services — Score: 212 #2/106
Services score of 212 spans Wells Fargo’s full service portfolio.
- Services: ADP, Adobe Analytics, Adobe Campaign, Adobe Creative Cloud, Adobe Creative Suite, Adobe Illustrator, Adobe Launch, Adobe Photoshop
Scale of services drives the integration-layer imperative.
Layer Summary: Services score of 212 reflects Wells Fargo’s breadth of enterprise SaaS consumption.
Layer 6: Integration & Interoperability
Evaluating Wells Fargo’s API, integration, event-driven connectivity.
Waves: MCP (Model Context Protocol), Agents, Skills
API — Score: 20 #32/106
API score of 20; concepts: API Gateways, API Securities, Capital Markets.
- Services: Amazon API Gateway, Apigee, Kong
- Concepts: API Gateways, API Securities, Capital Markets, Venture Capital, Web API, Working Capital
- Standards: HTTP, HTTP/2, JSON, OpenAPI, REST
Formalizing API standards is the most impactful integration move.
Integrations — Score: 36 #11/106
Integrations score of 36 spans Merge, Oracle Integration, Panora.
- Services: Merge, Oracle Integration, Panora
- Concepts: Cloud Integrations, Continuous Integration/Continuous Deployments, Continuous Integrations, Data Integrations, Integration Testing, Integration Tests, Integrations, System Integrations
- Standards: Enterprise Integration Patterns, Integration Patterns, SOA, Service Oriented Architecture
iPaaS reduces integration debt.
Event-Driven — Score: 23 #5/106
Event-Driven score of 23.
- Tools: Apache Flink, Apache Kafka, Apache NiFi, Apache Pulsar
- Concepts: Data Streamings, Event Driven, Event Management, Event Processing, Events, Fraud Preventions, Loss Events, Real-time Streamings
- Standards: Event Sourcing, Event-driven Architecture, Pub/Sub
Event streaming is foundational for real-time AI.
Patterns — Score: 19 #24/106
Patterns score of 19 on Spring, Spring Boot, Spring Cloud Stream.
- Tools: Spring, Spring Boot, Spring Cloud Stream, Spring Framework
- Concepts: Microservices, Pattern Recognitions, Patterns, Reactives
- Standards: Actor Model, Dependency Injection, Event-driven Architecture, Reactive Programming, SOA
Microservice patterns support AI workload scaling.
Specifications — Score: 10 #25/106
Specifications score of 10.
- Concepts: API Gateways, API Securities, Application Programming Interfaces, Capital Markets, Venture Capital, Web API, Web Services, Working Capital
- Standards: HTTP, HTTP/2, JSON, OpenAPI, Protocol Buffers, REST, TCP/IP, WebSockets
Elevating OpenAPI to enterprise standard creates shared vocabulary for AI.
Apache — Score: 15 #37/106
Apache score of 15: Apache AGE, Apache Airflow, Apache Ant, Apache Archiva, Apache Aries.
- Tools: Apache AGE, Apache Airflow, Apache Ant, Apache Archiva, Apache Aries, Apache Arrow, Apache Atlas, Apache BookKeeper
Apache ecosystem depth is a characteristic enterprise strength.
CNCF — Score: 27 #2/106
CNCF score of 27: Argo, Buildpacks, Consul.
- Tools: Argo, Buildpacks, Consul, Dex, Flux, Harbor, Jaeger, Kubernetes
CNCF maturity pairs with Kubernetes adoption.
Layer Summary: API (20) and Integrations (36) are the connective tissue for scaling AI.
Layer 7: Statefulness
Evaluating Wells Fargo’s Observability, Governance, Security, Data handling.
Waves: Memory Systems
Observability — Score: 53 #2/106
Observability score of 53 spans Azure Log Analytics, CloudWatch, Datadog.
- Services: Azure Log Analytics, CloudWatch, Datadog, Dynatrace, New Relic, SolarWinds, Splunk
- Tools: Elasticsearch, Jaeger, OpenTelemetry, Prometheus
- Concepts: Alerting, Application Performance Monitoring, Compliance Monitoring, Logging, Model Monitoring, Monitoring, Monitoring Tools, Observability
Consolidation lowers cost.
Governance — Score: 51 #38/106
Governance score of 51; standards: ISO, ITIL, ITSM.
- Concepts: Audits, Compliance, Compliance Management, Compliance Monitoring, Compliance Policies, Compliance Systems, Compliance Tools, Data Governance
- Standards: ISO, ITIL, ITSM, Lean Six Sigma, NIST, RACI, Six Sigma
Extending to AI governance is the natural evolution.
Security — Score: 82 #13/106
Security score of 82 anchored on Citrix NetScaler, Cloudflare, Microsoft Identity Manager.
- Services: Citrix NetScaler, Cloudflare, Microsoft Identity Manager, Palo Alto Networks
- Tools: Consul
- Concepts: Authentications, Authorizations, Data Encryptions, Encryptions, Information Security Frameworks, Security, Security Architectures, Security Best Practices
- Standards: IAM, ISO, NIST, SECURITY.md, SSL/TLS, SSO, SecOps, Security Standards
AI-specific security is a required add to existing program.
Data — Score: 129 #14/106
Data — Alteryx, Azure Data Factory, Crystal Reports anchors.
- Services: Alteryx, Azure Data Factory, Crystal Reports, Databricks, Power BI, Power Query, QlikSense, Snowflake
- Tools: Apache Airflow, Apache Hadoop, Apache Hive, Apache Iceberg, Apache Kafka, Apache NiFi, Apache Spark, ClickHouse
- Concepts: Analytics, Business Analytics, Business Intelligence, Data Analysis, Data Analysis Tools, Data Analytics, Data Analytics Platforms, Data Analytics Tools
- Standards: Data Modeling, Data Models
Continued cataloging and lineage pays off at AI scale.
Layer Summary: Observability (53), Governance (51), Security (82) reflect Wells Fargo’s operational maturity.
Layer 8: Measurement & Accountability
Evaluating Wells Fargo’s measurement discipline — Testing, Observability, DevEx, ROI.
Waves: Evaluation & Benchmarking
Testing & Quality — Score: 25 #29/106
Testing score of 25 with Appium, Playwright, Selenium.
- Tools: Appium, Playwright, Selenium, SonarQube
- Concepts: Acceptance Testing, Automated Testing, Automated Testing Frameworks, Automation Testing, Functional Testing, Integration Testing, Integration Tests, Product Testing
- Standards: Acceptance Criteria, SDLC, Six Sigma, Test Cases, Test Plans, Test Scripts
AI-specific evals extend traditional testing.
Observability — Score: 53 #2/106
Observability — Azure Log Analytics, CloudWatch, Datadog.
- Services: Azure Log Analytics, CloudWatch, Datadog, Dynatrace, New Relic, SolarWinds, Splunk
- Tools: Elasticsearch, Jaeger, OpenTelemetry, Prometheus
- Concepts: Alerting, Application Performance Monitoring, Compliance Monitoring, Logging, Model Monitoring, Monitoring, Monitoring Tools, Observability
Instrumented for AI workload observation.
Developer Experience — Score: 27 #15/106
DevEx score of 27 on Azure DevOps, GitHub, GitHub Copilot.
- Services: Azure DevOps, GitHub, GitHub Copilot, GitLab, IntelliJ IDEA, Pluralsight
- Tools: Docker, Git
DORA metrics and IDPs are next investments.
ROI & Business Metrics — Score: 60 #8/106
ROI score of 60 reflects Alteryx, Crystal Reports, Power BI.
- Services: Alteryx, Crystal Reports, Power BI, SAP, Tableau, Tableau Desktop
- Concepts: Business Analytics, Financial Accounting, Financial Analysis, Financial Analytics, Financial Crimes, Financial Data, Financial Engineering, Financial Instruments
ROI discipline translates naturally to AI initiatives.
Layer Summary: Measurement is necessary for accountable AI initiatives.
Layer 9: Governance & Risk
Evaluating Wells Fargo’s Regulatory, AI Review, Security, Governance, Privacy controls.
Waves: Governance & Compliance
Regulatory Posture — Score: 10 #68/106
Regulatory score of 10 with standards: ISO, Internal Control Standards, NIST.
- Concepts: Compliance, Compliance Management, Compliance Monitoring, Compliance Policies, Compliance Systems, Compliance Tools, Legal, Regulatory Compliances
- Standards: ISO, Internal Control Standards, NIST
Proactive alignment with NIST AI RMF is a forward investment.
AI Review & Approval — Score: 19 #51/106
AI Review score of 19 with Azure Machine Learning, OpenAI.
- Services: Azure Machine Learning, OpenAI
- Concepts: AI Platforms, Model Development, Model Lifecycle Management
- Standards: MLOps
Formalized AI review council is the priority governance investment.
Security — Score: 82 #13/106
Security — Citrix NetScaler, Cloudflare, Microsoft Identity Manager.
- Services: Citrix NetScaler, Cloudflare, Microsoft Identity Manager, Palo Alto Networks
- Concepts: Authentications, Authorizations, Data Encryptions, Encryptions, Information Security Frameworks, Security, Security Architectures, Security Best Practices
- Standards: IAM, ISO, NIST, SECURITY.md, SSL/TLS, SSO, SecOps, Security Standards
AI threat model coverage extends existing security.
Governance — Score: 51 #38/106
Governance standards: ISO, ITIL, ITSM.
- Concepts: Audits, Compliance, Compliance Management, Compliance Monitoring, Compliance Policies, Compliance Systems, Compliance Tools, Data Governance
- Standards: ISO, ITIL, ITSM, Lean Six Sigma, NIST, RACI, Six Sigma
AI governance as first-class discipline is the next step.
Privacy & Data Rights — Score: 4 #70/106
Privacy score of 4.
- Concepts: Data Protection, Privacy
Formal ‘training-eligible?’ classification prevents inadvertent PII use in models.
Layer Summary: Security (82), Governance (51), AI Review (19) shape the AI compliance envelope.
Layer 10: Economics & Sustainability
Evaluating Wells Fargo’s AI FinOps, Provider Strategy, Partnerships, Talent, Data Centers.
Waves: Cost Economics & FinOps, Supply Chain & Dependency Risk, Data Centers
AI FinOps — Score: 5 #32/106
AI FinOps score of 5 with Amazon Web Services, Azure Active Directory, Azure Data Factory.
- Services: Amazon Web Services, Azure Active Directory, Azure Data Factory, Azure Databricks, Azure DevOps, Azure Functions
- Concepts: Budgetings, Financial Plannings
Token-cost tagging required before AI spend accelerates.
Provider Strategy — Score: 14 #36/106
Provider Strategy score of 14 with Amazon API Gateway, Amazon ECS, Amazon Kinesis, Amazon S3.
- Services: Amazon API Gateway, Amazon ECS, Amazon Kinesis, Amazon S3, Amazon SNS, Amazon Web Services, Google Cloud Platform, IBM
- Concepts: Vendor Management
Explicit provider strategy tightens AI partnership decisions.
Partnerships & Ecosystem — Score: 17 #64/106
Partnerships score of 17 with Amazon API Gateway, Amazon ECS, Amazon Kinesis, Amazon S3.
- Services: Amazon API Gateway, Amazon ECS, Amazon Kinesis, Amazon S3, Amazon SNS, Amazon Web Services, Bloomberg, Bloomberg AIM
- Concepts: Cloud Ecosystems, Ecosystems, Platform Ecosystems
AI-specific partnerships are emerging.
Talent & Organizational Design — Score: 14 #62/106
Talent score of 14 with ADP, LinkedIn, PeopleSoft.
- Services: ADP, LinkedIn, PeopleSoft, Pluralsight, Workday
- Concepts: Artificial Intelligence/Machine Learning, Continuous Learning, Deep Learning, E-learnings, Human Resources, Learning, Machine Learning, Recruitings
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 (14) and Partnerships (17) most affect AI outcomes.
Layer 11: Storytelling & Entertainment & Theater
Evaluating Wells Fargo’s strategic narrative — Alignment, Standardization, M&A, Experimentation.
Waves: Moltbook, Gastown, Ralph Wiggum, OpenClaw / Clawdbot, Artificial General Intelligence (AGI)
Alignment — Score: 26 #19/106
Alignment score of 26; concepts: Application Architectures, Architecture Design, Architecture Strategies.
- Concepts: Application Architectures, Architecture Design, Architecture Strategies, Architectures, Business Transformations, Cloud Architectures, Cloud-native Architectures, Data Architectures
- Standards: Agile, Agile Methodology, Lean Management, Lean Manufacturing, SAFe Agile, Scrum
Aligning AI to business outcomes makes AI accountable.
Standardization — Score: 16 #43/106
Standardization score of 16: Agile, ISO, NIST, REST, SDLC.
- Standards: Agile, ISO, NIST, REST, SDLC, SQL, Standard Operating Procedures, Technical Specifications
Extending to AI (model cards, eval suites) is a natural evolution.
Mergers & Acquisitions — Score: 18 #23/106
M&A score of 18.
- Concepts: Due Diligences, Financial Modeling, Financial Models, M&AS, Mergers And Acquisitions
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 (26) and Standardization (16) shape AI program direction.
Strategic Assessment
Top Three 2026 Investment Recommendations for Wells Fargo
-
Establish an API-First Integration Layer. API score of 20 across 212 services leaves Wells Fargo 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 19 combined with AI adoption (score 67) 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 (15) and Event-Driven (23) 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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Access Review Campaign Generation
description: Access Review Campaign Generation — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: APM Latency Spike Investigation
description: APM Latency Spike Investigation — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Change Management Request Triage
description: Change Management Request Triage — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Data Quality SLO Check
description: Data Quality SLO Check — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Datadog Alert Fatigue Audit
description: Datadog Alert Fatigue Audit — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Employee Offboarding Revocation
description: Employee Offboarding Revocation — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Employee Onboarding Orchestration
description: Employee Onboarding Orchestration — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Enterprise Glossary Term Suggestions
description: Enterprise Glossary Term Suggestions — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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
Generate Weekly Executive Technology Digest — contextualized for Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: GitLab Pipeline Failure Triage
description: GitLab Pipeline Failure Triage — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Open Requisition Funnel Report
description: Open Requisition Funnel Report — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Opportunity Pipeline Health Alert
description: Opportunity Pipeline Health Alert — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: P1 Incident Response Orchestration
description: P1 Incident Response Orchestration — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Payroll Headcount Snapshot
description: Payroll Headcount Snapshot — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: PeopleSoft HR Data Sync
description: PeopleSoft HR Data Sync — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Risk Register Nightly Sync
description: Risk Register Nightly Sync — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Role Change Approval
description: Role Change Approval — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Salesforce Case Escalation
description: Salesforce Case Escalation — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: ServiceNow SLA Breach Prediction
description: ServiceNow SLA Breach Prediction — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Snowflake Warehouse Right-Sizing
description: Snowflake Warehouse Right-Sizing — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Splunk Dashboard Nightly Snapshot
description: Splunk Dashboard Nightly Snapshot — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Splunk Security Event Correlation
description: Splunk Security Event Correlation — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Stale Branch Cleanup
description: Stale Branch Cleanup — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Tableau Workbook Usage Audit
description: Tableau Workbook Usage Audit — contextualized for Wells Fargo 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 Wells Fargo 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://wells-fargo.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
Teams Meeting Transcript Summary — contextualized for Wells Fargo based on its actual service and tool footprint.
naftiko: '0.5'
info:
label: Teams Meeting Transcript Summary
description: Teams Meeting Transcript Summary — contextualized for Wells Fargo based on its actual service and tool footprint.
tags:
- microsoft-teams
- automation
capability:
exposes:
- type: mcp
namespace: teams-meeting
port: 8080
tools:
- name: execute
description: Teams Meeting Transcript Summary — contextualized for Wells Fargo based on its actual service and tool footprint.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: teams-meeting.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: teams-meeting
baseUri: https://wells-fargo.internal.example.com/teams-meeting/v1
authentication:
type: bearer
token: $secrets.teams_meeting_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Unified Customer Lookup Across Systems — contextualized for Wells Fargo 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 Wells Fargo 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 Wells Fargo 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://wells-fargo.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 Wells Fargo's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: api-developer
info:
label: Wells Fargo API Source Capability
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-api
baseUri: https://api.wells-fargo.example.com/v1
authentication:
type: bearer
token: $secrets.wells_fargo_api_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko source capability wrapping Wells Fargo's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: backend-developer
info:
label: Wells Fargo API Source Capability
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-api
baseUri: https://api.wells-fargo.example.com/v1
authentication:
type: bearer
token: $secrets.wells_fargo_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 Wells Fargo's capability fabric.
naftiko: '0.5'
naftiko_role_recommendation: chief-information-officer
info:
label: Wells Fargo Governance Capability
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Wells Fargo's capability fabric.
tags:
- naftiko
- applied-capability
- governance
- role:chief-information-officer
capability:
exposes:
- type: mcp
namespace: wells-fargo-governance
port: 8080
tools:
- name: execute
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Wells Fargo's capability fabric.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-governance.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-governance
baseUri: https://governance.wells-fargo.example.com/v1
authentication:
type: bearer
token: $secrets.wells_fargo_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 Wells Fargo's SREs and operators.
naftiko: '0.5'
naftiko_role_recommendation: cloud-architect
info:
label: Wells Fargo Operations Capability
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Wells Fargo's SREs and operators.
tags:
- naftiko
- applied-capability
- observability
- role:cloud-architect
capability:
exposes:
- type: mcp
namespace: wells-fargo-ops
port: 8080
tools:
- name: execute
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Wells Fargo's SREs and operators.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-ops.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-ops
baseUri: https://ops.wells-fargo.example.com/fabric/v1
authentication:
type: bearer
token: $secrets.wells_fargo_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 Wells Fargo's SREs and operators.
naftiko: '0.5'
naftiko_role_recommendation: cloud-engineer
info:
label: Wells Fargo Operations Capability
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Wells Fargo's SREs and operators.
tags:
- naftiko
- applied-capability
- observability
- role:cloud-engineer
capability:
exposes:
- type: mcp
namespace: wells-fargo-ops
port: 8080
tools:
- name: execute
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Wells Fargo's SREs and operators.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-ops.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-ops
baseUri: https://ops.wells-fargo.example.com/fabric/v1
authentication:
type: bearer
token: $secrets.wells_fargo_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 Wells Fargo's capability fabric.
naftiko: '0.5'
naftiko_role_recommendation: cloud-security-engineer
info:
label: Wells Fargo Governance Capability
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Wells Fargo's capability fabric.
tags:
- naftiko
- applied-capability
- governance
- role:cloud-security-engineer
capability:
exposes:
- type: mcp
namespace: wells-fargo-governance
port: 8080
tools:
- name: execute
description: Applied capability exposing governance metadata, policy compliance, and audit trails for Wells Fargo's capability fabric.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-governance.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-governance
baseUri: https://governance.wells-fargo.example.com/v1
authentication:
type: bearer
token: $secrets.wells_fargo_governance_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability that orchestrates Wells Fargo's data sources into a single MCP-ready pipeline for analytics and AI workloads.
naftiko: '0.5'
naftiko_role_recommendation: data-engineer
info:
label: Wells Fargo Data Pipeline Capability
description: Naftiko applied capability that orchestrates Wells Fargo'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: wells-fargo-data
port: 8080
tools:
- name: execute
description: Naftiko applied capability that orchestrates Wells Fargo'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: wells-fargo-data.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-data
baseUri: https://data.wells-fargo.example.com/pipelines/v1
authentication:
type: bearer
token: $secrets.wells_fargo_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 Wells Fargo's SREs and operators.
naftiko: '0.5'
naftiko_role_recommendation: director-of-cloud-engineering
info:
label: Wells Fargo Operations Capability
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Wells Fargo's SREs and operators.
tags:
- naftiko
- applied-capability
- observability
- role:director-of-cloud-engineering
capability:
exposes:
- type: mcp
namespace: wells-fargo-ops
port: 8080
tools:
- name: execute
description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Wells Fargo's SREs and operators.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-ops.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-ops
baseUri: https://ops.wells-fargo.example.com/fabric/v1
authentication:
type: bearer
token: $secrets.wells_fargo_ops_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: director-of-engineering
info:
label: Wells Fargo Platform Catalog Capability
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:director-of-engineering
capability:
exposes:
- type: mcp
namespace: wells-fargo-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-platform
baseUri: https://backstage.wells-fargo.example.com/api/catalog
authentication:
type: bearer
token: $secrets.wells_fargo_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: director-of-platform-engineering
info:
label: Wells Fargo Platform Catalog Capability
description: Source capability that publishes Wells Fargo'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: wells-fargo-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-platform
baseUri: https://backstage.wells-fargo.example.com/api/catalog
authentication:
type: bearer
token: $secrets.wells_fargo_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko source capability wrapping Wells Fargo's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: full-stack-developer
info:
label: Wells Fargo API Source Capability
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-api
baseUri: https://api.wells-fargo.example.com/v1
authentication:
type: bearer
token: $secrets.wells_fargo_api_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko source capability wrapping Wells Fargo's primary API surface, exposing it via MCP and REST for downstream reuse.
naftiko: '0.5'
naftiko_role_recommendation: head-of-api
info:
label: Wells Fargo API Source Capability
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api
port: 8080
tools:
- name: execute
description: Naftiko source capability wrapping Wells Fargo'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: wells-fargo-api.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-api
baseUri: https://api.wells-fargo.example.com/v1
authentication:
type: bearer
token: $secrets.wells_fargo_api_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Wells Fargo's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: head-of-integration
info:
label: Wells Fargo MCP Context Tool
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-context
baseUri: https://internal.wells-fargo.example.com/context/v1
authentication:
type: bearer
token: $secrets.wells_fargo_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: head-of-platform-engineering
info:
label: Wells Fargo Platform Catalog Capability
description: Source capability that publishes Wells Fargo'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: wells-fargo-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-platform
baseUri: https://backstage.wells-fargo.example.com/api/catalog
authentication:
type: bearer
token: $secrets.wells_fargo_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Wells Fargo's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: integration-architect
info:
label: Wells Fargo MCP Context Tool
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-context
baseUri: https://internal.wells-fargo.example.com/context/v1
authentication:
type: bearer
token: $secrets.wells_fargo_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Wells Fargo's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: mlops-engineer
info:
label: Wells Fargo MCP Context Tool
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-context
baseUri: https://internal.wells-fargo.example.com/context/v1
authentication:
type: bearer
token: $secrets.wells_fargo_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: platform-engineer
info:
label: Wells Fargo Platform Catalog Capability
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:platform-engineer
capability:
exposes:
- type: mcp
namespace: wells-fargo-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-platform
baseUri: https://backstage.wells-fargo.example.com/api/catalog
authentication:
type: bearer
token: $secrets.wells_fargo_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Wells Fargo's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: prompt-engineer
info:
label: Wells Fargo MCP Context Tool
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-context
baseUri: https://internal.wells-fargo.example.com/context/v1
authentication:
type: bearer
token: $secrets.wells_fargo_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Wells Fargo's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: solutions-architect
info:
label: Wells Fargo MCP Context Tool
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-context
baseUri: https://internal.wells-fargo.example.com/context/v1
authentication:
type: bearer
token: $secrets.wells_fargo_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Naftiko applied capability composed over Wells Fargo's existing source APIs, exposed as an MCP tool for agent context engineering.
naftiko: '0.5'
naftiko_role_recommendation: technical-lead
info:
label: Wells Fargo MCP Context Tool
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context
port: 8080
tools:
- name: execute
description: Naftiko applied capability composed over Wells Fargo'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: wells-fargo-context.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-context
baseUri: https://internal.wells-fargo.example.com/context/v1
authentication:
type: bearer
token: $secrets.wells_fargo_context_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
naftiko: '0.5'
naftiko_role_recommendation: vp-of-engineering
info:
label: Wells Fargo Platform Catalog Capability
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
tags:
- naftiko
- source-capability
- platform
- role:vp-of-engineering
capability:
exposes:
- type: mcp
namespace: wells-fargo-platform
port: 8080
tools:
- name: execute
description: Source capability that publishes Wells Fargo's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
inputParameters:
- name: context
in: body
type: string
description: Contextual parameter for the workflow.
call: wells-fargo-platform.execute
with:
context: '{{context}}'
consumes:
- type: http
namespace: wells-fargo-platform
baseUri: https://backstage.wells-fargo.example.com/api/catalog
authentication:
type: bearer
token: $secrets.wells_fargo_platform_token
resources:
- name: default
path: /actions/execute
inputParameters: []
operations:
- name: execute
method: POST
Score Breakdown — Total: 1656
Each row links to its full definition on the Naftiko Signal Groups page.
20 5 5 67 86 31 53 36 20 129 34 40 86 23 26 42 16 19 10 51 82 51 15 27 126 212 37 18 15 15 12 2 25 27 60 10 19 4 14 17 14Areas — Total: 1103
- .NET
- 3D
- AI Agents
- AI Platforms
- AI Solutions
- API Gateways
- API Securities
- Acceptance Testing
- Access Management
- Accessibility
- Accountability
- Accounting
- Accounting Systems
- Accounts Receivables
- Active Directory
- Ad Management
- Ad-teches
- Administration
- Administratives
- Agent Frameworks
- Agentic AI
- Agentic Frameworks
- Agentic Solutions
- Agentic Systems
- Agentics
- Agents
- Alerting
- Alerts
- Algorithmic Tradings
- Algorithms
- Analysis
- Analytics
- Anomaly Detections
- Application Architectures
- Application Development
- Application Lifecycle Management
- Application Performance Management
- Application Performance Monitoring
- Application Programming Interfaces
- Application Securities
- Application Servers
- Applications
- Architecture Design
- Architecture Strategies
- Architectures
- Artificial Intelligence
- Artificial Intelligence/Machine Learning
- Assessments
- Asset Liability Management
- Asset Management
- Asset Managers
- Assignments
- Asynchronous
- Audits
- Authentications
- Authorizations
- Automated Testing
- Automated Testing Frameworks
- Automation
- Automation Testing
- Autonomous Systems
- Awareness
- BI
- BPM
- Backends
- Backward Compatibilities
- Banking
- Banking Platforms
- Banking Technologies
- Bashes
- Batch Processing
- Benchmarkings
- Benchmarks
- Best Practices
- Big Data
- Billings
- Blockchains
- Bookings
- Bookkeepings
- Borrowings
- Bridges
- Budgetings
- Build Automation
- Build Pipelines
- Build Systems
- Building Automation
- Business
- Business Analysis
- Business Analytics
- Business Applications
- Business Continuities
- Business Intelligence
- Business Logics
- Business Management
- Business Models
- Business Operations
- Business Plannings
- Business Plans
- Business Process
- Business Solutions
- Business Strategies
- Business Tools
- Business Transformations
- Business to Consumers
- Business-to-Business
- CI
- CI/CD Pipelines
- Caches
- Caching
- Calendars
- Cameras
- Capital Markets
- Career Development
- Case Management
- Cash Management
- Cash Management Systems
- Cash Reconciliations
- Certificates
- Certifications
- Change Data Captures
- Change Management
- Chats
- Cities
- Claims Management
- Classification
- Clearings
- Client Data
- Client Experiences
- Client Management
- Client Relations
- Client Relationship Management
- Client Services
- Clients
- Cloud Adoptions
- Cloud Architectures
- Cloud Computing
- Cloud Data
- Cloud Data Platforms
- Cloud Databases
- Cloud Ecosystems
- Cloud Engineering
- Cloud Environments
- Cloud Infrastructure
- Cloud Integrations
- Cloud Landing Zones
- Cloud Migrations
- Cloud Natives
- Cloud Platforms
- Cloud Securities
- Cloud Services
- Cloud Storage
- Cloud Technologies
- Cloud-Based
- Cloud-native Architectures
- Cloud-native Development
- Cloud-native Platforms
- Cloud-native Tech
- Cloud-native Technologies
- Clouds
- Clustering
- Code Coverages
- Code Quality
- Code Reviews
- Codes
- Collaboration Tools
- Collaborations
- Collateral Management
- Collaterals
- Collections
- Command Lines
- Commerce
- Commodities
- Commodity Futures
- Communications
- Communities
- Compatibilities
- Compliance
- Compliance Management
- Compliance Monitoring
- Compliance Policies
- Compliance Systems
- Compliance Tools
- Computations
- Computer Aided Design
- Computer Aided Engineering
- Computer Aided Manufacturing
- Computer Applications
- Computer Sciences
- Computer Systems
- Computer Visions
- Computes
- Computing
- Conferences
- Configuration Management
- Configurations
- Connectivity
- Connectors
- Construction
- Consulting Services
- Consultings
- Contact Centers
- Contacts
- Container Orchestration
- Containerization
- Containerization Technologies
- Containerized Deployments
- Containers
- Content Delivery Networks
- Content Management
- Content Management Systems
- Contents
- Continuous Improvements
- Continuous Integration/Continuous Deployments
- Continuous Integrations
- Continuous Learning
- Contributions
- Control Planes
- Control Systems
- Controllers
- Controls
- Core Banking
- Core Systems
- Corporate Banking
- Corporate Finances
- Credit Applications
- Credit Cards
- Credit Management
- Credit Risks
- Critical Thinkings
- Cross Currency Swaps
- Cross Platforms
- Cryptographies
- Cs
- Currencies
- Custom Solutions
- Customer Engagements
- Customer Experiences
- Customer Journey Mappings
- Customer Journeys
- Customer Relationship Management
- Customer Satisfactions
- Customer Segmentations
- Customer Service
- Customer Support
- Customizations
- Cyber Defenses
- DNS, DHCP, and IP Address Management
- Dashboards
- Data
- Data Access
- Data Analysis
- Data Analysis Tools
- Data Analytics
- Data Analytics Platforms
- Data Analytics Tools
- Data Architectures
- Data Capabilities
- Data Captures
- Data Centers
- Data Cleansing
- Data Collections
- Data Encryptions
- Data Engineering
- Data Extractions
- Data Flows
- Data Foundations
- Data Governance
- Data Governance Strategies
- Data Handling
- Data Ingestions
- Data Integrations
- Data Integrity
- Data Interpretations
- Data Lakes
- Data Lineages
- Data Management
- Data Manipulations
- Data Mappings
- Data Marts
- Data Migrations
- Data Pipelines
- Data Platforms
- Data Processing
- Data Products
- Data Profilings
- Data Protection
- Data Quality
- Data Quality Frameworks
- Data Reconciliations
- Data Retrievals
- Data Sciences
- Data Securities
- Data Services
- Data Storage
- Data Strategies
- Data Streamings
- Data Structures
- Data Technologies
- Data Tools
- Data Transformations
- Data Validation
- Data Visualization Tools
- Data Visualizations
- Data Warehouses
- Data Warehousing
- Data Wranglings
- Data and Analytics
- Data-Driven
- Database Design
- Database Queries
- Database Technologies
- Databases
- Debuggings
- Decision Making
- Decision Support
- Deep Learning
- Defis
- Deliveries
- Dependencies
- Dependency Management
- Deployment Automation
- Deployment Practices
- Deployment Strategies
- Deployments
- Derivatives
- Derivatives Pricings
- Design
- Design Principles
- Design Reviews
- Design Thinkings
- Desktops
- Developer Experiences
- Developer Portals
- Development
- Development Lifecycle
- Development Practices
- Development Process
- Development Tools
- Diagnostics
- Differential Equations
- Digital Assets
- Digital Banking
- Digital Experiences
- Digital Products
- Digital Services
- Digital Solutions
- Digital Strategies
- Digital Systems
- Digital Tools
- Digital Transformations
- Digital Twins
- Digitals
- Directed Acyclic Graphs
- Directory
- Directory Services
- Disaster Recovery
- Distributed
- Distributed Applications
- Distributed Computing
- Distributed Systems
- Distributions
- Document Object Models
- Documentaries
- Documentations
- Documents
- Drift Detections
- Due Diligences
- Dynamics
- E-bankings
- E-learnings
- ERP
- ESB
- Ecommerce Platforms
- Ecommerces
- Economics
- Ecosystems
- Educations
- Efficiencies
- Electronic Data Interchange
- Electronic Tradings
- Emails
- Embeddings
- Employee Benefits
- Employee Experiences
- Employment
- Enablement
- Encryptions
- End To End
- Endpoint Protection
- Endpoint Securities
- Engineering
- Enterprise AI
- Enterprise Applications
- Enterprise Architectures
- Enterprise Content Management
- Enterprise Data
- Enterprise Risk Management
- Enterprise Risks
- Enterprise Securities
- Enterprise Software
- Enterprise Solutions
- Enterprise Systems
- Enterprises
- Entity Resolutions
- Equities
- Error Tracking
- Estate Plannings
- Evaluation Frameworks
- Evaluations
- Event Driven
- Event Management
- Event Processing
- Events
- Examples
- Excels
- Executions
- Experimentations
- Exploratory Data Analysis
- Extensions
- External Systems
- Extract Transform Loads
- Fault Tolerances
- Feature Engineering
- Feature Stores
- Feedback
- File Transfers
- Finances
- Financial Accounting
- Financial Analysis
- Financial Analytics
- Financial Crimes
- Financial Data
- Financial Engineering
- Financial Instruments
- Financial Modeling
- Financial Models
- Financial Operations
- Financial Plannings
- Financial Reportings
- Financial Services
- Financial Software
- Financial Stabilities
- Financial Systems
- Fintech
- Firewalls
- Fixed Incomes
- Flexibilities
- Flexible Workings
- Flinks
- Forecasting
- Forecasting Models
- Foreign Exchanges
- Forexes
- Formatting Objects Processors
- Forms
- Foundations
- Frameworks
- Fraud Detections
- Fraud Preventions
- Frenches
- Front-ends
- Frontend Development
- Frontends
- Full Stacks
- Functional Testing
- Functions
- Futures
- Gateways
- General Ledgers
- Generative AI
- Geographies
- GitHub Copilots
- Global Markets
- Google Cloud Functions
- Governance
- Governance Frameworks
- Government
- Graphical User Interfaces
- Graphics Processing Units
- Graphs
- HCM
- Hadoop Distributed File Systems
- Hardenings
- Hardware
- Healthcare
- Hedging
- High Availabilities
- High Performance Computing
- High Performances
- High Throughputs
- High-Frequency Tradings
- Hirings
- Hospitality
- Hosting
- Human Resources
- Hybrid Clouds
- IT Risk Management
- IT Risks
- IT Strategies
- IT and Operational Risks
- Ideas
- Identities
- Identity And Access Management
- Identity Management
- Implementations
- In-Memory Databases
- Incident Management
- Incident Responses
- Indexings
- Industry Analysis
- Inferences
- Information Securities
- Information Security Frameworks
- Information Systems
- Information Technologies
- Infrastructure
- Infrastructure As Codes
- Infrastructure Components
- Innovation
- Insights
- Institutional Finances
- Institutional Tradings
- Insurances
- Integrated Development Environments
- Integrated Solutions
- Integration Testing
- Integration Tests
- Integrations
- Integrity
- Intelligence
- Intelligent Systems
- Interactives
- Interfaces
- Internal Audits
- Internal Controls
- Internal Portals
- International Markets
- International Trades
- Internet
- Internet of Things
- Investment Analysis
- Investment Banking
- Investment Management
- Investments
- Invoice Processing
- Isolations
- Iterative Development
- Job Scheduling
- Journey Design
- Journey Mappings
- Key Metrics
- Key Risk Indicators (KRIs)
- Knowledge Bases
- Knowledge Graphs
- LLM
- Large Data Sets
- Large Datasets
- Large Language Models
- Leaderships
- Learning
- Ledgers
- Legacy Systems
- Legal
- Lendings
- Letters Of Credits
- Libraries
- Licensings
- Lifecycle Management
- Lightings
- Linear Algebras
- Liquidity Risk Management
- Load Balancers
- Load Balancings
- Loan Management Systems
- Loan Processing
- Log Management
- Logging
- Loss Events
- Low Latencies
- Low-Code Platforms
- M&AS
- Machine Learning
- Mails
- Mainframes
- Maintenance
- Management
- Management Systems
- Management Tools
- Mappings
- Market Data
- Market Intelligence
- Market Researches
- Market Risks
- Marketing
- Marketing Strategies
- Marketplaces
- Markets
- Massively Parallel Processing
- Mathematics
- Matrixes
- Measurements
- Media
- Mediations
- Meetings
- Mentoring
- Mergers And Acquisitions
- Meridians
- Messaging
- Messaging Infrastructure
- Messaging Systems
- Metadata
- Metadata Management
- Metadata Stores
- Metrics
- Micro-services
- Microservices
- Middle Offices
- Middlewares
- Migrations
- Mission Critical
- Mobile Banking
- Mobiles
- Model Calibrations
- Model Context Protocols
- Model Development
- Model Evaluations
- Model Governance
- Model Lifecycle Management
- Model Management
- Model Monitoring
- Model Orchestration
- Model Performance
- Model Validation
- Modeling
- Modernizations
- Modularity
- Monitoring
- Monitoring Tools
- Monte Carloes
- Multimodals
- Multiple Systems
- NLP
- Navigation
- Negotiations
- Network Access
- Network Automation
- Network Infrastructure
- Network Management
- Network Securities
- Networking
- News
- NoSQL
- Notebooks
- Notifications
- OLE for Process Controls
- ORM
- Object Storage
- Object Stores
- Object-Oriented
- Observability
- Observability Platforms
- Observability Stacks
- Observability Toolings
- Observability Tools
- Office Applications
- Office Suites
- On Demands
- Onboardings
- Online Analytical Processing
- Online Transaction Processing
- Open-source Programming Languages
- Operating Systems
- Operational Efficiencies
- Operational Excellence
- Operational Resiliences
- Operational Risk Frameworks
- Operational Risks
- Operational Technologies
- Operations
- Operations Management
- Operators
- Optical Character Recognitions
- Optimization Techniques
- Optimizations
- Options
- Orchestration
- Organizational Changes
- Organizational Structures
- Organizational Transformations
- Organizations
- Packages
- Packet Captures
- Panoramas
- Pattern Recognitions
- Patterns
- Payment Models
- Payment Processing
- Payment Solutions
- Payment Systems
- Payments
- Payments Applications
- Payroll
- Performance
- Performance Analysis
- Performance Engineering
- Performance Improvements
- Performance Management
- Performance Metrics
- Performance Monitoring
- Performance Optimizations
- Performance Tuning
- Pigs
- Pipeline Management
- Pipelines
- Pivot Tables
- Plannings
- Platform Development
- Platform Ecosystems
- Platform Engineering
- Platform Management
- Platform Services
- Platform Strategies
- Platforms
- Plugins
- Policies
- Portabilities
- Portals
- Portfolio Management
- Portfolio Reviews
- Predictive Modeling
- Presentations
- Pricing Models
- Pricings
- Prioritizations
- Privacy
- Private Clouds
- Probabilities
- Problem Resolutions
- Problem Solving
- Process Analysis
- Process Analytics
- Process Automation
- Process Controls
- Process Design
- Process Documentations
- Process Engineering
- Process Improvements
- Process Management
- Process Mappings
- Process Mining
- Process Modeling
- Process Optimizations
- Process Reengineerings
- Processes
- Product Areas
- Product Design
- Product Development
- Product Management
- Product Owners
- Product Roadmaps
- Product Strategies
- Product Testing
- Production
- Production Deployments
- Production Environments
- Production Support
- Production Systems
- Productivity
- Products
- Professional Development
- Profilings
- Program Management
- Programming
- Programming Languages
- Project Management
- Project Schedules
- Projects
- Prompt Engineering
- Prompts
- Protection
- Protocols
- Prototyping
- Provisionings
- Proxies
- Public Clouds
- Public Key Infrastructure
- QA
- Quality Assurance
- Quality Assurance Testing
- Quality Controls
- Quality Frameworks
- Quality Management
- Quality Metrics
- Quality Tools
- Quantitative Finances
- Quantitative Modeling
- Quantitative Models
- Query Optimizations
- Queues
- Reactives
- Real Estates
- Real Time
- Real-time Data
- Real-time Streamings
- Reasonings
- Reconciliations
- Record Keepings
- Recordings
- Recruitings
- Recruitment
- Registrations
- Regression Testing
- Regulatory Compliances
- Regulatory Reportings
- Regulatory Technologies
- Reinforcement Learning
- Relational Data
- Relational Database Management Systems
- Relational Databases
- Relationals
- Relationship Buildings
- Relationship Management
- Release Management
- Reliabilities
- Reliability Engineering
- Remittances
- Remote Access
- Remote Works
- Replications
- Reporting And Analytics
- Reporting Solutions
- Reporting Tools
- Reportings
- Requirements
- Requirements Gatherings
- Research
- Resiliences
- Resiliency
- Resource Allocations
- Resource Management
- Retails
- Reusable Components
- Revenue Generations
- Revenues
- Review And Approvals
- Reviews
- Rich Internet Applications
- Risk Analysis
- Risk Assessments
- Risk Management
- Risk Models
- Risk Systems
- Robotic Process Automation
- Robustness
- Root Cause Analysis
- Routings
- Runtimes
- Safes
- Safety
- Sales
- Sales Enablement
- Sales Enablement Tools
- Sanctions
- Sanctions Screenings
- Scalabilities
- Scaling
- Scannings
- Scenario Analysis
- Scenarios
- Scheduling
- Scientific Computing
- Scorings
- Screenings
- Scriptings
- Search
- Search Engine Optimizations
- Secrets Management
- Secure Coding Practices
- Secure Codings
- Secure Software Development
- Securities Lendings
- Securities Tradings
- Security
- Security Architectures
- Security Best Practices
- Security Controls
- Security Design
- Security Development Lifecycle
- Security Engineering
- Security Frameworks
- Security Incident Responses
- Security Information and Event Management
- Security Operations
- Security Requirements
- Security Risk Assessments
- Security Solutions
- Security Testing
- Security Tools
- Segmentations
- Semantic Searches
- Serverless
- Serverless Architectures
- Servers
- Service Deliveries
- Service Management
- Service Meshes
- Service Operations
- Services
- Settlements
- Shells
- Short Message Services
- Simulations
- Site Reliability Engineering
- Smart Contracts
- Social
- Social Media
- Software
- Software Configuration Management
- Software Deliveries
- Software Design
- Software Development
- Software Development Kits
- Software Engineering
- Software Platforms
- Software Solutions
- Software Systems
- Solutions
- Source Systems
- Sourcings
- Spreadsheets
- Stakeholder Management
- Standups
- State Machines
- State Management
- Static Analysis
- Static Application Security Testing
- Statistical Analysis
- Statistical Modeling
- Statistical Models
- Statistical Packages
- Statistics
- Stochastic Calculus
- Stochastic Processes
- Storage
- Stored Procedures
- Strategic Plannings
- Strategies
- Streamings
- Stress Testing
- Structured Data
- Structured Products
- Structured Streamings
- Subscriptions
- Supervised Learning
- Supply Chain Management
- Supply Chains
- Support
- Support Platforms
- Surveillances
- Switches
- System Administration
- System Architectures
- System Design
- System Development
- System Integrations
- System Of Records
- System Performances
- System Requirements
- System Stabilities
- System Testing
- Systems
- Systems Design
- Systems Development
- Systems Engineering
- Systems Programming
- Systems Testing
- Systems Thinkings
- T1S
- Tainas
- Tasks
- Taxes
- Team Development
- Technical Debt
- Technical Support
- Technologies
- Technology Architectures
- Technology Enhancements
- Technology Plannings
- Technology Services
- Technology Stacks
- Technology Strategies
- Telemetry
- Telewerkens
- Terminals
- Test Anything Protocols
- Test Automation
- Test Design
- Test Engineering
- Test Strategies
- Testing Frameworks
- Testing Strategies
- Testing Tools
- Tests
- Third Parties
- Third Party Risks
- Threat Management
- Threat Modeling
- Ticketing
- Ticketing Systems
- Tickets
- Time Management
- Time Series
- Time Series Databases
- Timelines
- Tokenizations
- Tokens
- Tools
- Total Rewards
- Tracing
- Tracking
- Tracs
- Trade Settlements
- Trade Surveillances
- Trading Platforms
- Trading Systems
- Tradings
- Training Data
- Trainings
- Transaction Banking
- Transaction Management
- Transaction Monitoring
- Transformations
- Transformers
- Translations
- Transparency
- Transportation
- Travels
- Treasuries
- Treasury Management
- Treasury Operations
- Treasury Solutions
- Troubleshooting
- Tuning
- UI
- UX
- Underwritings
- Unit Testing
- Unixes
- Unstructured Data
- Unsupervised Learning
- Updates
- Uptime
- Usabilities
- User Acceptance Testing
- User Experiences
- User Guides
- User Interface/User Experiences
- User Journeys
- Utilities
- Validation
- Validation Rules
- Validation and Testing
- Valuation Models
- Valuations
- Vector Databases
- Vendor Management
- Venture Capital
- Venues
- Verifications
- Version Control Systems
- Version Controls
- Versionings
- Video Chats
- Videos
- Virtualizations
- Visibility
- Visual Design
- Visualizations
- Voice
- Vulnerability Management
- Vulnerability Scannings
- Warehouse Technologies
- Wealth Management
- Web API
- Web Application Development
- Web Application Securities
- Web Applications
- Web Based
- Web Servers
- Web Services
- Web Sites
- Web Technologies
- Webs
- Wins
- Words
- Workflow Analysis
- Workflow Automation
- Workflow Orchestration
- Workflow Tools
- Workflows
- Workforce Management
- Working Capital
- Workshops
Services — Total: 212
- ADP
- Adobe Analytics
- Adobe Campaign
- Adobe Creative Cloud
- Adobe Creative Suite
- Adobe Illustrator
- Adobe Launch
- Adobe Photoshop
- Alteryx
- Amazon API Gateway
- Amazon ECS
- Amazon Kinesis
- Amazon S3
- Amazon SNS
- Amazon Web Services
- Ansible Automation Platform
- Apache Airflow
- Apache Software Foundation
- Apigee
- Artifactory
- Atlassian
- AutoCAD
- Autodesk Fusion 360
- Azure Active Directory
- Azure Data Factory
- Azure Databricks
- Azure DevOps
- Azure Functions
- Azure Kubernetes Service
- Azure Log Analytics
- Azure Machine Learning
- Azure Service Bus
- Azure Synapse Analytics
- Backstage
- BigCommerce
- Bitbucket
- Bloomberg
- Bloomberg AIM
- Bloomberg Economics
- Bloomberg Enterprise Data
- Bloomberg Intelligence
- Bloomberg News
- Box
- Bruno
- Calypso
- Checkmarx
- Circana
- Cisco
- Cisco Firepower
- Citrix NetScaler
- CloudFormation
- CloudWatch
- Cloudflare
- Confluence
- Crystal Reports
- Databricks
- Datadog
- Dealogic
- Dynatrace
- EC2
- F5 Networks
- FactSet
- Factiva
- Fern
- Figma
- G2
- GitHub
- GitHub Actions
- GitHub Copilot
- GitLab
- Gmail
- Google Analytics
- Google Apps Script
- Google Campaign Manager
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Forms
- Google Maps
- Google Optimize
- Google Search Console
- Google Sheets
- Harness
- HubSpot
- Hugging Face
- Hunter
- Hvault
- IBM
- IBM MQ
- IntelliJ IDEA
- International Business Machines
- Intuit
- Istio
- JFrog Artifactory
- Jira
- Juniper
- Juniper Networks
- Kinesis
- Kong
- Lightroom
- Linkerd
- MailChimp
- Make
- Mastercard
- Merge
- Meta
- Metasploit
- Microsoft
- Microsoft .NET
- Microsoft Azure
- Microsoft Copilot
- Microsoft Dynamics
- Microsoft Dynamics 365
- Microsoft Edge
- Microsoft Endpoint Manager
- Microsoft Entity Framework
- Microsoft Excel
- Microsoft Identity Manager
- Microsoft Office
- Microsoft Outlook
- Microsoft Planner
- Microsoft Power Apps
- Microsoft Power Automate
- Microsoft Power Platform
- Microsoft PowerPoint
- Microsoft Project
- Microsoft Purview
- Microsoft Teams
- Microsoft Visio
- Microsoft Windows
- Microsoft Word
- Navision
- New Relic
- OpenAI
- OpenAI APIs
- OpenShift
- Oracle
- Oracle Cloud
- Oracle E-Business Suite
- Oracle GoldenGate
- Oracle Integration
- Palo Alto Networks
- Panora
- PeopleSoft
- Perforce
- Photoshop
- Pluralsight
- Port
- Postman
- Power Apps
- Power BI
- Power Platform
- Power Query
- Productiv
- Qlik
- Qlik Sense
- QlikSense
- QlikView
- Qube
- Red Hat
- Red Hat Ansible Automation Platform
- Refinitiv
- SAP
- SAP BW
- SQL Server
- SailPoint
- Salesforce
- Salesforce Automation
- Salesforce Lightning
- Scalar
- ServiceNow
- SharePoint
- Shell
- Snowflake
- SolarWinds
- Solaris Zones
- Sparx Enterprise Architect
- Splunk
- Spot
- Square
- Sybase
- Tableau
- Tableau Desktop
- TeamCity
- Teradata
- Tradeweb
- Trellix Web Gateway
- Triton
- Tropic
- Unity
- Unix
- VMware
- Vantage
- Veritas InfoScale
- Veritas NetBackup
- Veritas Volume Manager
- Visio
- Visualforce
- WebSphere
- Windmill
- Workday
- Workday Security
- Youtube
- Zendesk
- ZoomInfo
- n8n
Tools — Total: 152
- Angular
- Ansible
- Ansible Playbooks
- Apache
- Apache AGE
- Apache Airflow
- Apache Ant
- Apache Archiva
- Apache Aries
- Apache Arrow
- Apache Atlas
- Apache BookKeeper
- Apache Camel
- Apache Cassandra
- Apache Commons
- Apache Cordova
- Apache DolphinScheduler
- Apache Drill
- Apache Flex
- Apache Flink
- Apache FreeMarker
- Apache Hadoop
- Apache Hive
- Apache Hop
- Apache Hudi
- Apache Iceberg
- Apache JMeter
- Apache James
- Apache Kafka
- Apache Knox
- Apache Kylin
- Apache MINA
- Apache Maven
- Apache NiFi
- Apache ORC
- Apache OpenJPA
- Apache OpenWebBeans
- Apache POI
- Apache Parquet
- Apache Phoenix
- Apache Pig
- Apache Pivot
- Apache Portals
- Apache Pulsar
- Apache Roller
- Apache Rya
- Apache SINGA
- Apache SkyWalking
- Apache SpamAssassin
- Apache Spark
- Apache Spatial
- Apache Streams
- Apache Synapse
- Apache TinkerPop
- Apache Tomcat
- Apache Traffic Control
- Apache Traffic Server
- Apache Web Services
- Apache XML Graphics
- Apache ZooKeeper
- Appium
- Argo
- BFE
- Backstage
- Buildpacks
- C#
- C++
- ClickHouse
- Cloud Custodian
- Consul
- Crossplane
- Cucumber
- Dex
- Docker
- Eclipse
- Elastic Stack
- Elasticsearch
- Elk Stack
- Ethereum
- FastAPI
- Flux
- Git
- Grafana
- HAMI
- Harbor
- Hashicorp Vault
- Helm
- Hibernate
- Hugging Face Transformers
- Istio
- Jaeger
- Jenkins
- Kafka Connect
- Keycloak
- Kibana
- Kotlin
- Kubeflow
- Kubernetes
- Kubernetes Operators
- Lean
- Linkerd
- Linux
- Logstash
- Matplotlib
- MongoDB
- MySQL
- Node.js
- NumPy
- Open Policy Agent
- OpenTelemetry
- PHP
- Packer
- Pandas
- Perl
- Pixie
- Playwright
- Porter
- PostgreSQL
- PowerShell
- Prometheus
- Pulumi
- Puppet
- PySpark
- PyTorch
- Python
- R
- Radius
- React
- React Native
- Redis
- Redux
- Rook
- SPIRE
- Scala
- Score
- Selenium
- Semantic Kernel
- Sonar
- SonarQube
- Spring
- Spring Boot
- Spring Cloud Stream
- Spring Framework
- Swift
- TensorFlow
- Terraform
- Vault
- Vitess
- WordPress
- bootc
- gRPC
- jQuery
Standards — Total: 159
- .prompt.md
- AIS
- Acceptance Criteria
- Accessibility Standards
- Accounting Standards
- Actor Model
- Agile
- Agile Methodology
- Architectural Design Patterns
- Architecture Pattern
- BDD
- BLE
- CITATION.cff
- CONTRIBUTING.md
- CONTRIBUTORS.md
- CSS
- Capital Requirements
- Certificate Enrolment Protocols
- Circuit Breaker
- Configuration Language
- Consensus
- DHCP
- DNS
- DSL
- Data Flow Diagrams
- Data Modeling
- Data Models
- Data Quality Standards
- Database Schema Design
- Defense In Depth
- Dependency Injection
- Design Patterns
- DevOps
- DevSecOps
- Domain-Driven Design
- Enterprise Integration Patterns
- Entity Relationship
- Equator Principles
- Event Sourcing
- Event-driven Architecture
- Extreme Programming
- FinOps
- Financial Regulation
- Flowcharts
- Functional Programming
- Gherkin
- GitOps
- Gremlin
- HTML
- HTML5
- HTTP
- HTTP/2
- IAM
- IMAP
- ISO
- IT Standards
- ITIL
- ITSM
- Integration Patterns
- Internal Control Standards
- JMS
- JPA
- JSON
- Jakarta EE
- Java EE
- Kanban
- LDAP
- LICENSE.md
- Lakehouse Architecture
- Lean Management
- Lean Manufacturing
- Lean Six Sigma
- MLOps
- MVC
- MapReduce
- Methodology
- NIO
- NIST
- OAuth
- OCI
- OIDC
- OWASP
- Object-Oriented Programming
- OpenAPI
- OpenID Connect
- Parquet
- Partitioning
- Process Flow Diagrams
- Product Backlog
- Product Backlog Items
- Protocol Buffers
- Prototypes
- Pub/Sub
- QoS
- Quality Of Service
- RACI
- RBAC
- RDP
- REST
- RPC
- Raft
- Reactive Programming
- Regulation
- Regulatory
- Runbooks
- SAFe Agile
- SAML
- SDLC
- SECURITY.md
- SOA
- SOAP
- SPA
- SQL
- SSL/TLS
- SSO
- SUPPORT.md
- Scaled Agile
- Schema Evolution
- Schema Validation
- Scrum
- SecOps
- Secure Software Development Life Cycle
- Secure Software Development Lifecycle
- Secure-by-Design
- Security Standards
- Security Standards And Procedures
- Service Oriented Architecture
- Services Patterns
- Six Sigma
- Software Design Architectural Patterns
- Software Design Patterns
- Software Development Life Cycle
- Software Development Lifecycle
- Specification
- Standard Operating Procedures
- Standardization
- Standards
- Swagger
- TCP/IP
- Table Format
- Technical Specifications
- Templates
- Test Cases
- Test First
- Test Plans
- Test Scripts
- Test-driven Development
- Use Cases
- User Stories
- VPN
- Waterfall
- WebSockets
- Wireframes
- Write Ahead Log
- XML
- Zero Trust
- Zero Trust Architecture
- Zero Trust Network Access
- Zero-Trust Security Model
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.