Operations | Monitoring | ITSM | DevOps | Cloud

Can you ban an idea? What we learned about open source at Civo Navigate London 2026

More and more, we are hearing how artificial intelligence is transforming how we build, secure, and share software. But as AI models become more powerful, questions around openness, security, and digital sovereignty are becoming harder to ignore. Can open models really be controlled? Is AI putting open-source communities under pressure? What does genuine technological independence look like? And who decides who gets access?

Deploying Apache Airflow on Aiven Runtime

When we first introduced people to Aiven Runtime, before it even had that name, we kept getting asked: "Can we schedule things?" If you come from a Unix background, that tends to cause a reflexive reach for the cron tool, which provides basic scheduling at fixed intervals. But if you've spent more time with distributed software, you're more likely to think of Apache Airflow, which can do a lot more (although, yes, you can use Airflow to schedule tasks at fixed intervals if you want).

All Things Open reminded me that Open Source is at the Heart of What We Do

That was the question posed at the Women in Open Source+ Panel I had been asked to moderate. The panelists, from Snowflake, AWS, and NVIDIA, gave similar answers: We have our jobs today because of the community, and I don’t see that changing any time soon. I felt the same. When I joined Aiven, its direct callout to open source was a deciding factor.

We just gave a million dollars to Open Source maintainers

The title is not a joke. For those of you who know Sentry, you know we’ve been giving back to Open Source maintainers since our early days in whatever ways we could. But around five years ago we really started to give in a more meaningful way. This year we increased our budget from $750,000 to $1,000,000.

Comparing Coralogix with open source observability backends

We put the same OpenTelemetry data into four backends, Coralogix, ClickHouse, OpenSearch and a Loki, Tempo and Prometheus stack, then set an agent twelve questions against each one, from counting spans to working out what is wrong in a system it has never seen. Then we forced the agents to continue investigating until they got to the right answer. In this experiment, what separated them was the time, tokens, tool calls and turns it took to get there.