Blog
-
Laravel 13 now supports MariaDB Vector natively

If your Laravel application runs on MariaDB, you can add semantic search to it without a second database, an external vector service or an extra package. Since Laravel 13.28, vector columns, vector indexes and similarity queries work on MariaDB out of the box. A large part of that work came from community contributors, including Mohamed Touhami Rhaima.
Until this summer, Laravel’s built-in vector search was a PostgreSQL feature: it assumed pgvector. Laravel’s AI SDK documentation now reads: “Vector queries are currently supported on […]
-
Frappe joins MariaDB Foundation as a Silver Sponsor

MariaDB Foundation welcomes Frappe as a Silver Sponsor.
Frappe builds open-source software for running organisations, including ERPNext, Frappe HR and Frappe CRM. Its applications are built on Frappe Framework, where MariaDB is the default database. That makes MariaDB part of the infrastructure behind the work Frappe users do every day, from managing finances and inventory to serving customers.
“Frappe shows what open-source software can deliver when the entire stack is available for people to use, adapt and improve,” said Anna […]
-
MariaDB Foundation Adds PostgreSQL to Its Engine‑Agnostic Testing Framework (TAF).
The Test Automation Framework (TAF) was designed so that database makers themselves could create a plugin and integrate their database engine directly into the framework.
TAF provides the structure — lifecycle management, workload execution, profiling, reporting, and reproducible properties files — and each database plugin supplies the engine‑specific logic.
The first two plugins added to TAF were MariaDB and MySQL, proving the model: database vendors can plug their engine into TAF and immediately gain automated installs, structured workloads, concurrency sweeps, […]
-
MariaDB Foundation: Auto‑Generated User Properties in TAF 4.0 — The Piece for Ensuring Full Test Reproduction
TAF’s reproducibility story just gained its most important upgrade: every test case now produces a fully resolved, auto‑generated user properties file.
This file captures exactly what the run used — not what the user intended, not what was passed in, but the final, authoritative configuration TAF executed. It removes ambiguity, eliminates hidden dependencies, and makes every test case a fully self‑describing artifact.
This feature builds directly on the work introduced in the previous blog, where TAF gained support for embedding […]
-
When AI Finds the Bugs We Missed: A Very Busy Year for MariaDB Security

You may have noticed that some recent MariaDB Server releases arrived a little later than expected. Sorry about that! But there is a good reason for it.
Over the last months, the MariaDB project has experienced something we had never seen before: a very large increase in security reports. And when I say large, look at this graph:
For years, we received a few security reports every quarter. Sometimes 3, sometimes 6, 11… the highest in the graph was 16.
-
MariaDB Foundation: TAF Now Supports Embedded Database Configuration in User Properties
TAF: One File to Rule Them All
In a one‑on‑one review of TAF with Monty Widenius, the creator of MySQL and MariaDB, he looked at me and said: “I want everything in one user file.”
It was simple, direct, and completely right direction.
TAF’s configuration model had inherited its design from older frameworks — a user properties file and a separate database configuration file.
Monty’s comment cut straight through it. He wanted simplicity — one file that defines everything.
So […]

