Marionete
Data and integration consultancy, Confluent partner
- records
- 1
- team
- 50-200
- founded
- 2016
Filter verified AI builders by what they build, who they serve, how they engage, and their regulatory readiness, and, on a separate axis, by how much they've proven.
167 providers
Data and integration consultancy, Confluent partner
Portuguese-owned systems integrator with a Kafka and data-integration practice.
AWS partner and event-driven architecture practice out of Vienna
Cork technology consultancy with a published cloud cost optimisation service
Digital consultancy with AI, DevOps and MLOps practices
Google Cloud Vertex AI implementation in LATAM
Positive digital flow
Snowflake Premier partner for legacy platform migration
Nippon Steel Group SI with a Snowflake DWH practice
Mitsui Group IT services firm with a Databricks migration practice
Skellefteå IT consultancy with a data and analytics practice serving telecom, industry and public sector
Copenhagen data consultancy, largest Snowflake partner in Denmark by certifications.
KCSP-certified Kubernetes and SRE partner
SRE and DevSecOps consulting across enterprise verticals
AWS-native serverless team with reliability automation
Kubernetes, DevOps, and platform engineering built on open-source stacks
Belgian DevOps shop specialised in Kubernetes, GitOps, and Prometheus
São Paulo consultancy running SRE, observability, and hybrid-cloud sustainment.
KubeOps and DevOps automation practice based in Diegem
Turning emerging tech into business impact on Azure
Cloud-native engineering boutique that co-hosts the Vienna Kafka meetup
DevOps, SRE, and cloud professional services across Kubernetes and CI/CD
SAP Platinum Partner with an SAP BW to cloud DWH modernisation practice
Multi-cloud services house with a dedicated Snowflake data practice.
Know what you need? Skip the scrolling.
Describe your work once, we route it to a few verified (L3+) builders you choose. Free, plan-blind, capped at three.
Ranked on proof, not pay-to-play. Default order is verification level, then record count, then recency, plan tier is never a factor. How we verify →