Maravilla Studio Enters Private Preview

Studio runs on each organization's own RaisinDB tenant on maravilla.cloud. It connects the systems an organization already uses, such as mailboxes, calendars, drives and payments, and brings them into one versioned database. Studio is already used in real projects, and from today further organizations can request an invitation.

In Plain Words

Most organizations keep their website in one tool, their ticket and product sales in another, their email and calendars somewhere else, and their routine processes in spreadsheets. Studio brings these together. A team edits pages directly on its website, sells tickets and products, works through a shared inbox, and turns a recurring checklist into an automation.

Studio can be used in two ways. People work in a polished web interface. AI assistants such as Claude, ChatGPT or Cursor can do the same work through the Model Context Protocol, within exactly the permissions of the user who connected them. We think of agents as an interface to Studio in their own right, not as an add-on to it.

Built on RaisinDB, and Shaped by It

Much of what Studio can do comes from the database underneath. RaisinDB keeps content, relationships, vectors and full-text search in one place, versions everything with Git-like branches, and enforces row-level security in the database itself. It records which user or agent changed what, keeps credentials in an encrypted vault, and speaks MCP in both directions: as a server that assistants connect to, and as a client that uses tools offered by other MCP servers.

RaisinDB is source-available. Studio is the product Maravilla Labs builds on top of it: the applications, the web interface, the automations, the commerce engine, the ready-made connections and the MCP servers that make all of it usable by teams and by agents.

Agents as an Interface, Next to a Polished Web App

MCP servers: Studio's content and events are available to AI assistants over MCP. An assistant can draft and publish pages, translate content, build an event programme or look up ticket sales.
Brand over MCP: Brand kits, including voice, tone and vocabulary, are served to agents too, so text and layouts produced by an assistant match the organization's brand.
AI-assisted coding: Partners build on Studio together with coding assistants. More than thirty detailed Studio skills teach those assistants how Studio works, from content and automations to commerce, payments and Microsoft 365, so that small teams can build complete websites and business applications in days or weeks.
Same rules: Agents act through the same roles and row-level security as the people who connect them, and because every change is versioned, their work can be reviewed before it goes live.

Virtual Mounts: Connect Anything

A central idea in Studio comes from RaisinDB: virtual mounts. An external system, such as a mailbox, a calendar, a drive or a business application, is mounted into a part of the database. Its items appear as ordinary content, so search, permissions, automations, agents and the audit log work on an email or a calendar entry exactly as they do on a page.

Mounts also write back. A mounted calendar entry can be edited and the change goes to the source; for an email, only its state, such as read or flagged, is changed; and a node can act as a command, such as sending a reply. Out of the box, RaisinDB includes adapters for Microsoft 365 mail, calendars, OneDrive and SharePoint, Google Drive and Google Calendar, and IMAP mailboxes. Connectors can ship ready-made sets of mounts that an administrator creates in one step.

Studio builds on this with a shared inbox and a calendar across all connected calendars, both working directly on the mounted data.

Managed Connectors

On maravilla.cloud, Maravilla Connect makes these connections a one-click step. Organizations connect Microsoft 365, Google Drive and Stripe through applications registered and maintained by Maravilla, instead of registering their own with each provider. The broker handles the token exchange and does not keep users' access tokens. Organizations that run RaisinDB themselves can still connect the same systems with their own provider registrations.

Automations With Agentic Steps

The automation workbench lets teams draw a process as a graph and run it on RaisinDB's flow engine. A step can be a function, a task assigned to a person or a group, or an agentic step: a bounded conversation with a language model that ends with structured output the next step can rely on. Because connected mailboxes and drives are content, an incoming email or a new file can start an automation. A runs view shows what each automation actually did.

Events and a Commerce Engine

Studio manages events from the programme to the door: agenda, speakers and venues, partners and sponsorship tiers, ticket sales with card payments through Stripe, tickets with QR codes, door check-in that works without a network connection, and session sign-ups with a waiting list that moves up automatically.

Behind the ticketing sits a general commerce engine: shops and a product catalogue, stock kept as a ledger, memberships and donations with receipts, and invoice numbering designed to hold up in an audit. Parts of the commerce engine are new and are being opened up step by step during the preview.

Websites and Content

Inline editing: Editors change text, images and sections directly on the page they are looking at, with drafts that stay private until they are ready.
Publishing: Publishing based on database branches, with scheduled publishing and a four-eyes approval step where it is required.
Linked sites: Country and language versions and campaign microsites created from blueprints and kept in sync with their source.
Brand kits: Visual identity and verbal identity stored as data and exportable as design tokens.
Framework SDKs: Websites are built with React, Svelte or Vue and connected to Studio through small SDKs.

What Studio Is Used For

Studio is already used in real projects, and further setups are being prepared. Without naming the organizations, these are the kinds of work it does:

An AI conference: organizers maintain the programme, speakers and ticket prices in Studio and the public site updates without a redeployment. Visitors buy tickets on their phone without creating an account, and an AI agent describes, titles and files uploaded media.
An importer of industrial products: a website in English and Japanese, and quotes and orders that staff price, approve and send from inside an AI assistant, with each order running as a long-lived process with approval steps and deadlines.
A sports club, in preparation: match fixtures with seating categories, season tickets, a fan shop, memberships and donations in one content package, with tickets, receipts and member cards generated as PDFs.
A fiduciary office, as a ready-made template: an invoice sent to the office mailbox is filed with the right client, its fields are read and it becomes a booking line; uncertain documents become a review task. The entire setup ships as content, without code.
A company operating system, being built by a partner: a second brain that keeps a company's mail, files, people, projects and orders in one connected graph, with agents that can work across all of it.

Six Months of Building

Studio's first version was released on 10 July 2026. By the end of August, it had seen more than 500 commits and more than twenty tagged releases. It builds on the work Maravilla Labs has announced since February:

February: maravilla.cloud opens to partner organizations.
May: realtime, authentication, durable workflows and media processing on the edge runtime, and RaisinDB as a managed service.
June: applications on maravilla.cloud can serve tools to AI assistants over MCP.
July: a regional newsroom pilots its editorial workflow on the platform.
August: RaisinDB 0.3 adds MCP as server and client, an audit trail and a secrets vault.

Private Preview

The preview is by invitation. Participating organizations are onboarded directly by the Maravilla Labs engineering team, get their own RaisinDB tenant on maravilla.cloud and influence what is finished first. Not every part of Studio is final: parts of the commerce engine are still being opened up, and some areas, such as augmented-reality content, are explicitly experimental.

Organizations that would like to take part can request an invitation at hello@maravillalabs.com.

About Maravilla Labs

Maravilla Labs is a software research laboratory based in Basel, Switzerland focused on building original developer infrastructure. The lab develops systems for source control, software distribution, hosting, and runtime execution with an emphasis on simplicity, security, and open architecture.

Projects developed by Maravilla Labs include systems for git hosting, package registries, CI and CD execution, edge runtime infrastructure, the versioned content database RaisinDB and Maravilla Studio.

Media Contact

Email: hello@maravillalabs.com

Location: Basel, Switzerland 🇨🇭

Maravilla Labs does not employ a public relations agency. Media enquiries are handled directly by engineering and founding staff.