About Us

About Beetl

Vienna-based team building and operating custom data integrations. We keep the source-specific mappings explicit and run ingestion, transformation, validation and recovery on one platform.

Our Mission

Every custom integration tends to become its own application. A team writes the extraction code, the mapping logic, the transformation, the target writes, the retries, the logs, the deployment configuration, and the monitoring. The first successful data transfer creates a false sense that the integration is finished.

We ran into this ourselves at a previous company. The difficult part was rarely making the first request to an API. The difficult part was building an integration that stayed understandable and reliable once it became part of production.

Beetl exists so that work stops being rebuilt for every source and every destination. The genuinely custom part stays explicit and inspectable. Credential handling, scheduling, transformation, validation, deployment and recovery run on one platform, and we operate it.

1 flow
one source, one destination, the smallest useful engagement
4-8 weeks
to a running, versioned data flow we operate
Read-only
source systems stay untouched by default

Who We Are

Vienna-based, Europe-focused

We are building Beetl from Vienna for European teams who need their integrations to keep working, without standing up an integration platform of their own.

Data Engineering DNA

Our team has built software for data-intensive systems: large event streams, multi-terabyte pipelines, and integrations where reliability mattered more than novelty.

One flow at a time

We start with one source, one destination, and one defined data flow. Every engagement leaves behind something running and versioned that we operate, not a report about what should be built.

Our Team

We've built data platforms at hyperscale. Now we're building the layer that keeps custom integrations running.

Michele Vigilante

Michele Vigilante

Co-Founder, CEO

Data engineer, conference speaker, and open source contributor. Spent the last 10 years building SaaS platforms, most recently re-architecting the data stack for a programmatic ad-tech product.

Bougouma Fall

Bougouma Fall

Co-Founder, CTO

Software engineer with a knack for connecting hardware to data. Built medical device integrations in health-tech and engineered large-scale data pipelines in ad-tech.

Ray Kameda

Ray Kameda

Co-Founder, CPO

Technical product manager and data strategist. Spent the last 12 years turning complex operational data into products people love, from incubating businesses at Hitachi to building energy IoT platforms.

Selected experience and technologies

Apache DataFusion logoKubernetes logoAVEVA logoAWS logoRust logoOpen Source Initiative logoDelta Lake logoGoogle Cloud logoOSIsoft logo
Hitachi logoKPMG logo

Trust floor

Read-only by default

Beetl reads from the systems your business already depends on without changing them. Writes go only to destinations you have explicitly approved.

EU-hosted and GDPR-aware

Infrastructure is hosted in Europe and built around European data protection expectations. Customer deployments and credentials stay isolated. Read our privacy policy.

Reaches systems that stay inside

For operational systems that cannot be reached from outside your network, a locally deployed site connector synchronizes approved data to Beetl's EU-hosted cloud.

Start with the one that costs you the most.

Tell us what breaks, what it feeds, and who notices when it goes wrong. We will scope the smallest flow that removes it, or say honestly that it is not a fit.

Talk to us