Claris Studio is ending on 15 March 2027

What Claris announced

In August 2026, Giuliano Iacobelli, VP of Product at Claris, published an official announcement confirming that Claris Studio will be discontinued effective 15 March 2027.

The announcement was candid: despite growing adoption, Studio was not scaling at the rate required to support continued investment. Claris acknowledged that product gaps were not closed quickly enough, and that AI-powered web application generators narrowed Studio's opportunity to secure a lasting position in the market.

For customers who invested time building solutions in Studio, this is significant news with a hard deadline. The service will remain available until shutdown, but there is no path to keep Studio running beyond March 2027.

What it means if you use Studio today

• Apps keep running until 15 March 2027. Existing published apps and web forms will continue to function normally through the transition period.
• Data export is available now. You can export your data at any time using the CSV table export feature. After shutdown, all Studio data will be securely deleted under Claris's retention policy.
• Studio URLs die on the day. Links will stop working on 15 March 2027 with no per-form redirects. Any shared URLs need to be replaced before shutdown.
• FileMaker, Connect, and MCP are unaffected. Claris FileMaker continues active development. Claris Connect and Claris MCP for FileMaker remain available and are not being discontinued.
• No licence-price reduction. Studio was bundled into FileMaker plans, so there is no pricing change as a result of the discontinuation.

Why Claris's suggested path is not enough

Claris's official alternatives are FileMaker WebDirect for authenticated portals and third-party form tools like Typeform, JotForm, or Tally (via Claris Connect or the Data API) for anonymous data collection.

For most Studio customers, this is a step backwards:

• WebDirect is an internal-tool delivery layer. It does not deliver SEO-friendly public pages, single-page-app performance, or the UX standards customers expect from a 2026 web product. It is not a replacement for customer-facing portals, dashboards, or branded web experiences. (See our WebDirect vs modern web stack guide for an honest comparison.)
• Typeform is a form, not a product. If your Studio deployment was a data entry form, Typeform may work. If it was a portal, dashboard, approval workflow, or any kind of application with logic, Typeform does not replace it.
• You lose the integration. Studio connected forms directly to FileMaker data. Stitching Typeform to FileMaker via Connect or the Data API is possible, but it is plumbing you have to build and maintain yourself.

Studio customers typically need portals, dashboards, anonymous data capture, and brand-level UX — exactly the things WebDirect and a form tool cannot deliver together.

The Neptune replacement: TypeScript + Next.js

Neptune Digital has been transitioning customers off Claris Studio (and off WebDirect for customer-facing use cases) for years. The architecture is straightforward:

• A lightweight TypeScript/Next.js front-end deployed to Vercel, Cloudflare, or a UK provider.
• Connected to your existing FileMaker system via the FileMaker Data API.
• FileMaker remains the system of record — the database, the script engine, the business logic. The web stack is the user-facing layer.

This is the same architecture we recommend for any customer-facing FileMaker deployment, and it is the upgrade Studio never was.

What you unlock vs Studio

Cost: less than a year of Studio licensing

A typical Neptune Digital Studio replacement — a lightweight TypeScript/Next.js web application connected to your existing FileMaker system — costs less than what a year of Claris Studio licensing used to cost as a standalone product, and a fraction of rebuilding in WebDirect plus a form tool.

You get a richer, faster, more capable product that you own outright. No per-view caps, no platform dependencies, no shutdown deadline hanging over it.

For detailed UK pricing context, see our FileMaker development cost guide.

How a transition works

1. Inventory your Studio deployment. What views and forms are in production? What data flows to and from FileMaker? Who uses it?
2. Export your data. Use Studio's CSV export to back up anything stored in Studio tables (not FileMaker).
3. Scope the replacement. We map your Studio functionality to a Next.js architecture — often simpler than what you had in Studio, because you are not working around platform limitations.
4. Build against FileMaker. The new front-end connects to your existing FileMaker system via the Data API. FileMaker remains the system of record.
5. Parallel run. Run both systems side-by-side to validate data and user flows.
6. Cut over shared URLs. Replace Studio URLs with your new domain before 15 March 2027 — URLs you control permanently.

Timeline: do not wait until Q1 2027

From today, you have roughly six months until Studio shuts down. That is enough time for a well-planned transition, but not enough time for a rushed one.

If you wait until January 2027 to start, you will be competing for agency capacity with every other Studio customer who also waited. Start the conversation now, even if you are not ready to build immediately.

See also: Extend & Modernise Your FileMaker System, FileMaker WebDirect vs Modern Web Stack, and Is FileMaker Still Worth Using in 2026?