Blog & Insights

WP_Query Object ( [query] => Array ( [post_type] => post [showposts] => 8 [orderby] => Array ( [date] => desc ) [autosort] => 0 [paged] => 4 [post__not_in] => Array ( ) ) [query_vars] => Array ( [post_type] => post [showposts] => 8 [orderby] => Array ( [date] => desc ) [autosort] => 0 [paged] => 4 [post__not_in] => Array ( ) [error] => [m] => [p] => 0 [post_parent] => [subpost] => [subpost_id] => [attachment] => [attachment_id] => 0 [name] => [pagename] => [page_id] => 0 [second] => [minute] => [hour] => [day] => 0 [monthnum] => 0 [year] => 0 [w] => 0 [category_name] => [tag] => [cat] => [tag_id] => [author] => [author_name] => [feed] => [tb] => [meta_key] => [meta_value] => [preview] => [s] => [sentence] => [title] => [fields] => all [menu_order] => [embed] => [category__in] => Array ( ) [category__not_in] => Array ( ) [category__and] => Array ( ) [post__in] => Array ( ) [post_name__in] => Array ( ) [tag__in] => Array ( ) [tag__not_in] => Array ( ) [tag__and] => Array ( ) [tag_slug__in] => Array ( ) [tag_slug__and] => Array ( ) [post_parent__in] => Array ( ) [post_parent__not_in] => Array ( ) [author__in] => Array ( ) [author__not_in] => Array ( ) [search_columns] => Array ( ) [ignore_sticky_posts] => [suppress_filters] => [cache_results] => 1 [update_post_term_cache] => 1 [update_menu_item_cache] => [lazy_load_term_meta] => 1 [update_post_meta_cache] => 1 [posts_per_page] => 8 [nopaging] => [comments_per_page] => 50 [no_found_rows] => [order] => DESC ) [tax_query] => WP_Tax_Query Object ( [queries] => Array ( ) [relation] => AND [table_aliases:protected] => Array ( ) [queried_terms] => Array ( ) [primary_table] => wp_posts [primary_id_column] => ID ) [meta_query] => WP_Meta_Query Object ( [queries] => Array ( ) [relation] => [meta_table] => [meta_id_column] => [primary_table] => [primary_id_column] => [table_aliases:protected] => Array ( ) [clauses:protected] => Array ( ) [has_or_relation:protected] => ) [date_query] => [request] => SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND ((wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'expired' OR wp_posts.post_status = 'acf-disabled' OR wp_posts.post_status = 'tribe-ea-success' OR wp_posts.post_status = 'tribe-ea-failed' OR wp_posts.post_status = 'tribe-ea-schedule' OR wp_posts.post_status = 'tribe-ea-pending' OR wp_posts.post_status = 'tribe-ea-draft'))) ORDER BY wp_posts.post_date DESC LIMIT 24, 8 [posts] => Array ( [0] => WP_Post Object ( [ID] => 5227 [post_author] => 7 [post_date] => 2026-05-18 14:50:12 [post_date_gmt] => 2026-05-18 14:50:12 [post_content] => [post_title] => Workshops & Assessments: AI Enablement Workshop for Infrastructure [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => ai-enablement-workshop-for-infrastructure-and-operations-teams [to_ping] => [pinged] => [post_modified] => 2026-06-01 15:44:48 [post_modified_gmt] => 2026-06-01 15:44:48 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5227 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [1] => WP_Post Object ( [ID] => 5224 [post_author] => 7 [post_date] => 2026-05-15 15:33:37 [post_date_gmt] => 2026-05-15 15:33:37 [post_content] => Most engineering leaders I talk to can tell you roughly what their cloud bill looks like. “Somewhere around $150K a month.” “Azure went up again this quarter.” “AWS feels higher than it should.” But if you ask where the spend is actually coming from, things get fuzzy pretty quickly. Which teams are driving the increase? How much of the spend is production versus lower environments? How many resources are sitting mostly idle? How much storage has been accumulating for years because nobody wants to risk deleting it? Those answers are usually harder to get than people anticipate. And honestly, that’s understandable. Cloud environments evolve fast. New subscriptions get added. Teams spin up workloads to solve immediate problems. Projects end, but the infrastructure behind them doesn’t always disappear with them. Over time, the cloud bill becomes something organizations react to instead of something they actively manage. We see it constantly. Development environments running full weekends because nobody ever implemented shutdown automation. Large database tiers sized for peak usage that only happens a few days a month. Old snapshots, unattached disks, forgotten load balancers, reserved instance opportunities nobody had time to evaluate. None of it looks catastrophic on its own. Together, it becomes real money. That’s why we stopped approaching cloud cost optimization as a “recommendation exercise.” Most teams already know they probably have waste. Usually, the problem is not that teams are ignoring cloud costs. It’s that the cleanup work never becomes urgent enough to pull people away from delivery deadlines, production support, or platform work already in flight. Most environments already have savings opportunities sitting there - somebody just needs the time to trace through the billing data, validate what is actually being used, and make the changes carefully enough that nothing critical gets disrupted. That was really the reason we turned this into a structured sprint instead of just another assessment. The engagement starts with discovery and billing analysis across the environment. We look at tagging quality, utilization trends, resource inventory, and how costs break down across teams, applications, and environments. The goal is to get past generalized assumptions and identify where spend is actually occurring. From there, we move into analysis and prioritization. Compute right-sizing, storage cleanup opportunities, licensing optimization, lifecycle automation gaps, and unused resources all get reviewed with projected savings attached to each item. But the important part is implementation. We apply the quick wins during the engagement itself. Budget alerts. Automated shutdown schedules for dev and test workloads. Tagging enforcement. Infrastructure-as-code updates for repeatable governance patterns. By the end of the sprint, organizations are usually already seeing measurable reductions in spend. One recent engagement involved an organization operating across eight Azure subscriptions with monthly cloud costs around $180,000. In that environment, lower-tier workloads were basically running all the time whether anybody was using them or not. Tagging standards had drifted differently across teams over the years, and several systems had simply been sized larger and larger without anyone revisiting whether the capacity was still necessary. About six weeks later, monthly spend was down by close to $20,000. There was no major migration project behind it and no application redesign effort. Most of the improvement came from cleaning up the environment, tightening governance a bit, and fixing the kind of operational drift that slowly builds up in long-running cloud environments. Nobody wants an open-ended consulting engagement just to figure out why their cloud bill increased. In most cases, the savings offset the engagement cost fairly quickly. The long-term value is usually bigger than the initial savings anyway. Once teams finally have visibility into where costs are coming from, and with some basic guardrails in place, the environment tends to stay much healthier over time instead of gradually drifting back into the same patterns. At a certain point, most organizations can tell when the cloud bill has turned into something they simply accept every month instead of something they actively manage. That’s usually the point where it makes sense to step back and take a closer look at it. Download our Cloud Cost Optimization sprint overview [table id=3 /] [post_title] => Your Cloud Bill Is an Unmonitored Process. Here's How to Trace It. [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => why-your-cloud-bill-keeps-growing-and-how-to-fix-it [to_ping] => [pinged] => [post_modified] => 2026-05-15 15:33:37 [post_modified_gmt] => 2026-05-15 15:33:37 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5224 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [2] => WP_Post Object ( [ID] => 5218 [post_author] => 7 [post_date] => 2026-05-12 19:00:44 [post_date_gmt] => 2026-05-12 19:00:44 [post_content] => I've had some version of the same conversation with engineering leaders more times than I can count: "Our pipelines aren't great… but we know what's wrong. We just need time to fix it." A couple years ago, I would've nodded and moved on. Now I push back. Not because they're wrong, but because they're usually only seeing part of it. In almost every environment we've assessed, teams can point to a handful of real problems. Slow builds. Flaky deployments. Maybe some test instability that everyone has quietly agreed to tolerate. Those things are real, and they matter. But they're rarely what keeps me up at night. What we keep finding are the things that stopped feeling like problems years ago. Long-lived credentials that were supposed to be temporary. Branch protections that exist in the settings but get bypassed under deadline pressure. Pipeline logic that was copy-pasted between repositories and has since drifted in six different directions. No one made a bad decision, things just accumulated. Individually, none of it feels urgent. But when you look at the whole picture, the exposure adds up fast. The engagement that really changed how we work was with a large clothing retailer. Experienced platform team. Mature Terraform usage. Years of GitHub CI/CD in production. On paper, they were further along than most. When we got into the details, the story got more complicated. Four different branching conventions had developed across teams over five years. SonarQube was configured, but enforcement was inconsistent depending on who had merged last. There was no documented recovery process if something went seriously wrong with the pipeline or the repository state. None of it was catastrophic in isolation, but none of it was actually under control either. Rather than handing them a list of things to fix, we ran a structured assessment. Direct repository and pipeline analysis. Stakeholder interviews. A look across version control hygiene, CI/CD design, security posture, testing strategy, GitOps alignment — the full system, not just the symptoms the team had already named. The output wasn't a slide deck. It was a prioritized roadmap with effort and impact scores - something the team could actually sequence and execute, not file away. That difference matters more than it sounds. Most pipeline advice ends up in a document somewhere. What teams actually need is someone telling them: this is what to fix first, this is what can wait, and here's why. It's why we changed how we structure this work. Short, focused engagements. Direct technical analysis, not just interviews. Something concrete at the end - not just a framework, not just a set of principles, but a sequenced implementation plan. If your pipelines have been running for a few years without that kind of outside look, there's a reasonable chance you're carrying more risk than the team realizes. That's not a knock on anyone, it's just how systems evolve when people are heads-down shipping. The question worth sitting with is whether you want to find out on your own terms, or wait until an audit, an incident, or a frustrated engineering leader forces the conversation. Get more information on our pipeline assessment and optimization. [table id=3 /] [post_title] => Why We Stopped Giving Pipeline Advice and Started Doing the Work [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => why-we-stopped-giving-pipeline-advice-and-started-doing-the-work [to_ping] => [pinged] => [post_modified] => 2026-05-12 19:00:44 [post_modified_gmt] => 2026-05-12 19:00:44 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5218 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [3] => WP_Post Object ( [ID] => 5209 [post_author] => 7 [post_date] => 2026-04-28 18:42:03 [post_date_gmt] => 2026-04-28 18:42:03 [post_content] => A few months ago, I was on a call with a mid‑sized financial services firm. They had a solid security team and capable engineers. Nothing about the organization suggested risk or immaturity. During the conversation, I asked a simple question: how many TLS certificates are you managing? The answer was roughly 180. Then I asked how renewals were tracked. The response: spreadsheets, a shared drive, and calendar reminders. It was concerning, but not surprising. Just six months earlier, I had the exact same conversation with a healthcare organization managing more than 300 certificates the same way. Despite the risk, this approach is far more common than most teams are comfortable admitting. What’s changing now is scale. The CA/Browser Forum has approved a progressive reduction in maximum TLS certificate lifetimes, culminating in a 47‑day limit by 2029, with significant reductions beginning as early as 2026. For teams that renew certificates annually today, this represents an eightfold increase in renewal activity per domain. For that financial services client, 180 certificates quickly translate into more than 1,400 renewal events per year. With their existing process, this was not an operational problem waiting to happen. It was a structural failure already underway. As we worked through the implications together, the initial instinct was predictable: add more process. Better spreadsheets. Tighter ownership. Escalation procedures. We challenged that assumption early. Process does not scale at this magnitude. No amount of procedural rigor can compensate for an eightfold increase in repetitive, time‑sensitive work. Automation is not an optimization here. It is the only viable answer. What we ultimately built, and have since deployed for several organizations facing the same challenge, is an Ansible‑based automation pipeline that manages the full certificate lifecycle end to end. Certificate signing request generation. Submission to the certificate authority. Deployment across a wide range of endpoints, including web servers, load balancers, and Kubernetes clusters. Post‑deployment validation to ensure certificates are live and correctly installed. Event‑Driven Ansible plays a critical role. Instead of relying on humans to track expiration dates, the system continuously monitors live endpoints, local certificate stores, and Kubernetes secrets. When a certificate approaches its renewal threshold, the pipeline is triggered automatically. No manual checks. No calendar reminders. No late‑night surprises. Equally important were the less visible pieces. Integration with secrets management so private keys never leave their source systems. A complete audit trail suitable for compliance and security reviews. And a local test harness that allowed engineers to run the full lifecycle safely in their own environment before anything touched production. That last element matters more than most teams realize. Trust in automation comes from watching it work, repeatedly, in a controlled setting. Three months after go‑live, something interesting happened. On‑call pages for expired certificates stopped entirely. The system did its job quietly in the background, which is exactly how critical infrastructure should behave. The security team gained auditable evidence they could provide to regulators without manual effort. The platform team reclaimed hours previously lost to renewal toil. And when we compared the avoided manual effort against the cost of implementation, the payback period was under eight months, even before factoring in the cost of downtime or customer impact from an outage. The broader takeaway is simple. Organizations should assess their certificate exposure now, before the 2026 reductions take effect. The solution itself is not complex, but implementing it properly takes time. Six to eight weeks is typical, and that timeline compresses dramatically once a mandate is already in force. Teams that act early will barely notice the transition. Teams that wait until 47 days becomes the standard will find themselves scrambling to automate eight renewals per year per domain while still delivering on every other commitment on their roadmap. The spreadsheet era of certificate management is ending. That outcome is already written into policy. The only remaining question is whether your organization gets ahead of it or reacts when the pressure arrives. Learn more about CertOps Automation. [table id=3 /]   [post_title] => The 47 Day Certificate Problem No One Is Talking About (Yet) [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => the-47-day-certificate-problem-no-one-is-talking-about-yet [to_ping] => [pinged] => [post_modified] => 2026-06-01 14:08:51 [post_modified_gmt] => 2026-06-01 14:08:51 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5209 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [4] => WP_Post Object ( [ID] => 5202 [post_author] => 7 [post_date] => 2026-03-17 13:48:01 [post_date_gmt] => 2026-03-17 13:48:01 [post_content] => Over the years, I’ve realized that most security conversations aren’t really about the tools. They’re about trade-offs. Every leadership team wants speed, faster releases, and more agility. But at the same time, no one wants to be the subject of a breach or sit through a painful audit that didn’t go well. The real ask is always the same - convenience versus security. And honestly, pretending you can maximize both without compromise just doesn’t work. That’s why it is important to ground infrastructure decisions in CIS benchmarks from the Center for Internet Security. It gives everyone a starting point that’s practical and recognized. This is not just for internal teams, but also to be used by regulators and auditors. Instead of debating what “secure enough” means in a meeting for an hour, we anchor to a baseline that already aligns with PCI, HIPAA, NIST, and other frameworks organizations need to follow. In client environments, especially healthcare and financial services, we’ve rolled out CIS benchmarks across Red Hat Enterprise Linux and Windows Server environments in a couple of ways. Sometimes that means deploying hardened images from the start. Other times it’s remediating what’s already there through automation. Both of these approaches work, depending on where the organization is in its journey. On cloud platforms like AWS, Azure, and GCP, pre-configured CIS images make adoption and deployment faster. You’re not bolting security later on, since it’s there from day one. For organizations under regulatory pressure, it matters. It reduces risk, yes; but also reduces friction, which is harder to quantify but just as important. Where I’ve seen the biggest shift, though, is when hardening becomes part of the DevOps flow instead of a separate security checkpoint. Using Ansible, we’ve automated high-risk patching and tied CIS-CAT reporting directly into delivery pipelines. So, compliance checks aren’t a quarterly readout, they are continuous and baked in. And when exceptions do come up, they’re intentional and all captured in version control (git). That changes the tone of the conversation and it moves security from reactive to engineered. At the end of the day, security that slows the business down won’t last. It’ll get bypassed. But security that’s automated, repeatable, and embedded into release processes and organization wide becomes an enabler. When CIS hardening lives inside images, pipelines, and patch workflows, organizations get more than compliance. They get confidence. And in my experience, confidence and reduced risk is what actually allows teams to move faster not slower. View the infographic. [table id=3 /] [post_title] => Embedding CIS Hardening into DevOps to Reduce Risk [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => cis-hardening [to_ping] => [pinged] => [post_modified] => 2026-03-17 14:03:29 [post_modified_gmt] => 2026-03-17 14:03:29 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5202 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [5] => WP_Post Object ( [ID] => 5177 [post_author] => 7 [post_date] => 2025-09-26 22:56:10 [post_date_gmt] => 2025-09-26 22:56:10 [post_content] => Discover how leading organizations are transforming their IT operations with the Keyva Seamless Data Pump™. This eBook details how you can automate complex integrations, achieve true single pane-of-glass visibility, and streamline your entire IT infrastructure—without the need for deep developer expertise.

• Automate data flows across your enterprise for real-time, accurate insights.
• Boost operational efficiency and eliminate manual, error-prone processes.
• Accelerate ROI with plug-and-play solutions, vendor-certified apps, and global support.
• Empower your teams to focus on business outcomes, not integration headaches.

Ready to modernize your IT operations and unlock the full potential of your data? Download the eBook to learn how Keyva can help you build a future-ready enterprise. [table id=3 /] [post_title] => Create Seamless Integrations to Support Single Pane-of-Glass Visibility [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => create-seamless-integrations-to-support-single-pane-of-glass-visibility-2 [to_ping] => [pinged] => [post_modified] => 2025-09-26 22:59:10 [post_modified_gmt] => 2025-09-26 22:59:10 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5177 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [6] => WP_Post Object ( [ID] => 5174 [post_author] => 7 [post_date] => 2025-09-26 22:22:18 [post_date_gmt] => 2025-09-26 22:22:18 [post_content] => To get the most out of your AI initiatives and infuse intelligence into your core business processes, you must first establish an IT environment that is “intelligent” itself. In other words, intelligence breeds intelligence. Without establishing a modernized foundation that is automated, adaptable and anticipatory, your AI initiatives will struggle to scale, adapt, or deliver the ROI you hoped. Just as a successful business strategy hinge on the people, process, and technology, your enterprise IT ecosystem requires embedded intelligence across its key pillars. These pillars are known as infrastructure, operations, development, applications, and governance. Let’s explore these five pillars in greater detail and reimagine how AI can elevate each one. 1. AI-Driven Infrastructure Modernization The first step is to ensure that your on-prem infrastructure is intelligence ready. This requires hardware prerequisites such as GPUs, latest and compatible hardware, deployment of containers and kubernetes, modern DevOps base layer, and more. Once your infrastructure readiness is achieved, you can introduce AI into your operational and automation tasks that were traditionally done manually or using disparate scripts. These tasks include things such as patching, resource planning, storage management, capacity planning and forecasting. When done in a proactive manner these efforts streamline the right-sizing of virtual machines, making optimization faster, smarter, and more efficient. Businesses must move from a reactive mindset of manual responses to a proactive anticipatory strategy that only AI can deliver. The ability to readily identify usage patterns will enable forward-thinking resource and capacity planning that will then unlock other advanced capabilities:

• Order new infrastructure resources ahead of time so you don't run into capacity shortages that could disrupt operations.
• Track compute resource performance to identify underutilized or overwhelmed systems and suggest optimizations for better cost management.
• Fully leverage historical trends and usage patterns to achieve smarter long-term planning and budgeting.

2. AI-Driven Operations Alerts are constantly coming into your NOC or SOC informing you that servers are down or unusual login activity is occurring. How do you keep up with it all? The primary objective of AI enabled operations is to find the underlying cause by correlating all the things that are happening within your enterprise and connecting the dots. Root cause analysis becomes possible only when you can see how different events relate to each other. For instance, a single authentication alert may not mean much on its own, but when you connect it to another event ID, a pattern appears. In other cases, an alert may point to the wrong culprit as a server being down may be a failed network switch upstream. Having a current and accurate CMDB (Configuration Management Database) is critical for generating correlations, and determining other CIs (Configuration Items) that can potentially be affected. Automatic proactive notifications can be set to trigger when abnormal patterns occur, so that the operations teams get notified and trigger the appropriate and timely response. That may sound simple on the one hand and daunting on the other, but AI makes this possible by removing the guesswork from incident response. This means that your support teams can react faster and more consistently, which directly strengthens both your system's resilience and overall security. Another emerging feature of AI Ops is the utilization of chatbots, which allows teams to ask questions in normal conversation format and get real answers concerning things such as ticket status or procedural steps around specific workflows. 3. AI-Enhanced Developer Productivity Many organizations have gained great efficiency for their development teams by using IDE integrations and internal large language models. AI solutions like GitHub Copilot and internal large language models now assist in code validation and linting, processes that could eat up hours of manual work. Developers use AI capabilities embedded into their IDE consoles to gain efficiencies with the programming tasks. The payoff of these automation efforts is almost immediate, as bugs get caught earlier in the process, code quality improves, readability increases, and teams spend far less time on tedious manual reviews. What used to require multiple rounds of human oversight now happens automatically, freeing developers to focus on solving bigger problems. 4. AI Integrated Applications Whether it is commercial off-the-shelf applications or applications customized for your own organization, AI can take them to the next level. Imagine an application making API calls to the client's on-premises LLM to solicit AI-generated suggestions for infrastructure optimization that can then be presented to end users as action items. Consider another instance in which an application continuously monitors infrastructure usage patterns, automatically suggesting practical steps like storage deletion, re-tiering, or resource reallocation. AI-enhanced applications are doing far more than just providing data. They deliver context-aware insights that adapt to your specific environment and business needs. That means faster response times, reduced operational overhead and greater strategic use of resources. 5. AI for Governance, Security, and Trust One of the keys for security today is the ability to identify unanticipated activity. An example could be a privileged user that logs in from a new geographic location, device, or time window. AI detectors can easily identify these abnormalities and initiate alerts that then require validation by the security team. If these events cannot be validated, security policies should then kick in automatically to protect against these events. Essentially, the system learns what "normal" looks like for each user and environment, then acts decisively when patterns break. This level of intelligent governance creates a powerful defense mechanism that stops unauthorized activity in its tracks while maintaining operational flow for legitimate users. When governance is implemented effectively, it can stop any activity that is not part of the pattern, improving business resiliency and trust. AI-driven governance is especially valuable in industries with strict compliance requirements, like healthcare and finance, where monitoring and enforcing policy adherence is critical. Keyva as Another Pillar At Keyva, we focus on the infrastructure and operational backbone that powers your business. While your core business processes may require industry-specific expertise, we ensure your IT infrastructure is smart, responsive, and ready to support whatever your organization builds on top of it. We have proven specialties when it comes to transforming all five pillars of your IT ecosystem and we invite your technology and business leaders to discover how our expertise can help modernize your entire IT landscape to unlock greater agility, performance, and resilience for your enterprise. [table id=3 /] [post_title] => The Five Pillars of Intelligent Enterprise IT Modernization [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => the-five-pillars-of-intelligent-enterprise-it-modernization [to_ping] => [pinged] => [post_modified] => 2025-09-26 22:24:58 [post_modified_gmt] => 2025-09-26 22:24:58 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5174 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [7] => WP_Post Object ( [ID] => 5187 [post_author] => 13 [post_date] => 2025-09-24 21:34:10 [post_date_gmt] => 2025-09-24 21:34:10 [post_content] =>

https://youtu.be/5Uob3eBvm4A

Keyva CTO Anuj Tuli discusses how an acquisition of a leading data integration platform help enhance our offerings in the DevOps and cloud automation space.

[post_title] => CTO Talks: IP and Integrations [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => cto-talks-ip-and-integrations [to_ping] => [pinged] => [post_modified] => 2025-12-15 22:02:06 [post_modified_gmt] => 2025-12-15 22:02:06 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5187 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) ) [post_count] => 8 [current_post] => -1 [before_loop] => 1 [in_the_loop] => [post] => WP_Post Object ( [ID] => 5227 [post_author] => 7 [post_date] => 2026-05-18 14:50:12 [post_date_gmt] => 2026-05-18 14:50:12 [post_content] => [post_title] => Workshops & Assessments: AI Enablement Workshop for Infrastructure [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => ai-enablement-workshop-for-infrastructure-and-operations-teams [to_ping] => [pinged] => [post_modified] => 2026-06-01 15:44:48 [post_modified_gmt] => 2026-06-01 15:44:48 [post_content_filtered] => [post_parent] => 0 [guid] => https://keyvatech.com/?p=5227 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [comment_count] => 0 [current_comment] => -1 [found_posts] => 174 [max_num_pages] => 22 [max_num_comment_pages] => 0 [is_single] => [is_preview] => [is_page] => [is_archive] => [is_date] => [is_year] => [is_month] => [is_day] => [is_time] => [is_author] => [is_category] => [is_tag] => [is_tax] => [is_search] => [is_feed] => [is_comment_feed] => [is_trackback] => [is_home] => 1 [is_privacy_policy] => [is_404] => [is_embed] => [is_paged] => 1 [is_admin] => [is_attachment] => [is_singular] => [is_robots] => [is_favicon] => [is_posts_page] => [is_post_type_archive] => [query_vars_hash:WP_Query:private] => 78786a6e639c29b4db7d53856140c66c [query_vars_changed:WP_Query:private] => [thumbnails_cached] => [allow_query_attachment_by_filename:protected] => [stopwords:WP_Query:private] => [compat_fields:WP_Query:private] => Array ( [0] => query_vars_hash [1] => query_vars_changed ) [compat_methods:WP_Query:private] => Array ( [0] => init_query_flags [1] => parse_tax_query ) [query_cache_key:WP_Query:private] => wp_query:bba64d078b07c53f642cc119ead65aa5 [tribe_is_event] => [tribe_is_multi_posttype] => [tribe_is_event_category] => [tribe_is_event_venue] => [tribe_is_event_organizer] => [tribe_is_event_query] => [tribe_is_past] => )