Skip to content

Blog

Why I'm Shutting Down Taleshape Cloud

A few months ago I launched a Cloud offer — a hosted version of Shaper where you could sign up and get a managed instance.

The “Cloud” was really just a signup form. I then set up instances manually for people who were interested. I shared it on LinkedIn and was happy to see that some of you were actually interested and wanted to try it out.

But building a complete self-serve Cloud product requires a lot more work than adding a few more features to open source Shaper. Billing, onboarding, provisioning, multi-tenancy, auto-scaling.

In the months after the Cloud launch, I saw something else happening:

I started getting more customers for my original service offering: helping companies run Shaper in their own infrastructure and integrate it into their product.

I started to see a clear pattern. The companies turning to Shaper are in healthcare and other regulated industries. They want embedded analytics dashboards as code and need complete data sovereignty. They want to use AI to build analytics but can’t send data to third-party vendors.

This is the use case I had in mind from the beginning when I started building Shaper. And getting more customers confirmed it. So I want to focus on what’s working instead of trying to build for multiple use cases in parallel.

So I decided to double-down on the original idea. From now on Taleshape has a single offer: managed hosting and hands-on support for companies that want help running Shaper and building with it.

We deploy Shaper in your infrastructure, handle security monitoring, and deliver updates as Pull Requests you review. And we help with integrations, dashboard development, and compliance.

From the start I’ve been adding features to Shaper that alternative tools only offer in their enterprise editions — SSO, embedded analytics with row-level security, white labeling. I considered creating a separate, paid version, but I never did. I knew it would make things more complex and as a solo developer I couldn’t afford complexity.

Now I’m making this more explicit. There is no paid edition of Shaper. Every feature is and stays open source. What my customers actually pay me for is the service around it: personal support, fast issue resolution, compliance consultation, help integrating Shaper into their product, and prioritizing features — not access to functionality.

I think this is the right approach. The open source project gets stronger. Guaranteed no vendor lock-in. No conflict of interest between the open source project and the business. And the service I offer is still valuable on its own.

I know there is genuine interest in an easy-to-use, self-serve platform around Shaper’s “Dashboards as SQL” approach.

But instead of trying to build that myself, I’m looking for companies building data platforms that might want to offer Shaper as part of their hosted product.

If that’s you, please reach out!

If you’re in healthcare or another regulated industry and looking for help implementing embedded analytics with full data sovereignty, let’s talk.

And if you just want to build dashboards with SQL on your own server or laptop, Shaper is free and open source. Every feature included.

Thank you!
Jorin

What DuckDB 2.0 Means for Shaper

Have you seen the DuckDB 2.0 release two weeks ago and wondered what that means for Shaper?

Shaper allows you to build analytics dashboards all in SQL. And that SQL runs directly in DuckDB.

So what does the DuckDB 2.0 release mean for Shaper? What’s new? Will this break your setup? And when will Shaper switch to DuckDB 2.0?

Some of the biggest changes are technical internals:

DuckDB 2.0 has a new SQL parser and new extension APIs which allow for more flexible extensions. This is exciting news for anyone building DuckDB extensions, and I am looking forward to seeing what people will do with this in the coming months.

There are also new features:

  • A VARIANT type, which is similar to storing unstructured JSON but faster.
  • SQL triggers, which are relevant if you are actively updating data in DuckDB, though less so if you only query data.

Read the announcement post for all the details.

The biggest thing is likely raw performance:

DuckDB 2.0 has been rewritten to use async I/O and can be much faster now when querying files from S3 or similar object storage.

Apart from that, there are some nice syntax improvements.

The most relevant for Shaper users is the new variable syntax. Instead of writing:

WHERE org = getvariable('org_id')

You can now write:

WHERE org = $org_id

I am definitely looking forward to this one.

Short: Not anytime soon.

The biggest reason is that we take backward compatibility seriously. DuckDB 2.0 is clearly a breaking change.

We also think it’s best to wait for the first bug fix release and to ensure all major extensions have caught up.

Our current plan is to switch once we release Shaper 1.0, which in itself will be a release that we use to make a few breaking changes to clean up Shaper.

Shaper 1.0 is unlikely to come before Q2 2027.

We are tracking the progress for that on GitHub here.

Dashboards as Code for your dbt Project

dbt is great for transforming data. You write modular SQL, track everything in Git, and run automated tests to make sure your data is correct.

But dbt doesn’t help you visualize your data.

When it’s time to build dashboards on top of a dbt project, you usually end up clicking around in a separate BI tool - outside of Git and disconnected from your code workflow.

That’s where Shaper comes in: In Shaper, dashboards are also just SQL files stored in Git.

Clinic Overview Dashboard Preview

Recently Jarich, creator of model2data, and I built a demo project to show how simple it is to go from a data model to a tested dbt project and an interactive Shaper dashboard.

We auto-generated the dbt project with model2data then, generated the Shaper dashboard with a single AI prompt.

You can check out the live dashboard and the code right here:

When building a demo, fake data is usually a pain. If you just generate random values, all your charts look flat and unrealistic. Or the data doesn’t even make sense - like invoices dated before an appointment was booked, or payments on cancelled visits.

That’s the problem Jarich solved with model2data.

For our demo, we modeled a network of 8 healthcare clinics with practitioners, treatments, insurers, patients, and appointments in a single schema file.

With model2data, you define your schema once and specify how the generated data should behave:

# Excerpt from healthcare_clinics.model2data.yml
appointments:
role: fact
columns:
status:
type: appointment_status
not_null: true
generate:
weights: {completed: 16, cancelled: 3, no_show: 1}
booked_at:
type: timestamp
not_null: true
generate: {growth: 0.5}
scheduled_for:
type: timestamp
not_null: true
generate: {after: booked_at, business_hours: true}
actual_duration_minutes:
type: int
generate:
min: 10
max: 120
when: {status: [completed]}
distribution: {kind: normal, mean: 35, stddev: 12}
billed_amount:
type: numeric
generate:
min: 25
max: 600
when: {status: [completed]}
distribution: {kind: lognormal, median: 95, spread: 0.5}
paid_at:
type: timestamp
generate:
after: checked_in_at
when: {status: [completed]}
null_rate: 0.3

From this single file, model2data generates:

  1. A DuckDB database with 1,500 patients and 6,000 appointments scheduled during realistic weekday business hours.
  2. A complete dbt project with staging models and 83 automated dbt data tests - checking primary keys, foreign key relationships, non-null constraints, and valid status values.

Once you have a ready dbt project, building dashboards in Shaper follows the exact same workflow. Shaper directly connects to the database generated by model2data and queries the exact tables dbt defined.

Shaper is directly built on top of DuckDB and lets you build interactive dashboards completely in SQL:

  • Dashboards live as .dashboard.sql files right next to your dbt models in Git.
  • You use standard DuckDB SQL and turn results into filters, metrics, and charts using custom SQL types like ::DROPDOWN, ::BARCHART_STACKED, or ::LINECHART.
  • Because dbt already tests your foreign keys and constraints, you can join tables and calculate metrics without worrying about broken references or messy data.

Here is how Clinic Overview.dashboard.sql sets up filters at the top and caches the filtered dbt tables in a temporary table for fast queries across the dashboard:

-- 1. Main Header & Controls
SELECT 'Healthcare Clinic Network'::SECTION, 'Executive Overview & Clinical Operations'::SUBTITLE;
SELECT
min(scheduled_for)::DATE::DATEPICKER_FROM AS start_date,
max(scheduled_for)::DATE::DATEPICKER_TO AS end_date
FROM staging.stg_appointments;
SELECT 'Clinic'::LABEL;
SELECT 'All Clinics'::DROPDOWN AS selected_clinic
UNION ALL
(SELECT name FROM staging.stg_clinics ORDER BY name);
-- 2. Cache filtered dataset in memory
CREATE TEMP TABLE filtered_appointments AS (
SELECT
a.id AS appointment_id,
a.status,
a.channel,
a.booking_source,
a.scheduled_for,
a.actual_duration_minutes,
a.billed_amount,
a.paid_at,
c.name AS clinic_name,
p.specialty AS practitioner_specialty,
t.name AS treatment_name,
COALESCE(i.name, 'Uninsured / Self-Pay') AS insurer_name
FROM staging.stg_appointments a
JOIN staging.stg_practitioners p ON a.practitioner_id = p.id
JOIN staging.stg_clinics c ON p.clinic_id = c.id
JOIN staging.stg_treatments t ON a.treatment_id = t.id
JOIN staging.stg_patients pat ON a.patient_id = pat.id
LEFT JOIN staging.stg_insurers i ON pat.insurer_id = i.id
WHERE a.scheduled_for::DATE BETWEEN getvariable('start_date') AND getvariable('end_date')
AND (getvariable('selected_clinic') = 'All Clinics' OR c.name = getvariable('selected_clinic'))
);

From there, every chart on the dashboard is just a simple SQL query:

SELECT 'Monthly Appointments by Status'::LABEL;
SELECT
date_trunc('month', scheduled_for)::DATE::XAXIS,
status::CATEGORY,
count(*)::BARCHART_STACKED
FROM filtered_appointments
GROUP BY ALL
ORDER BY ALL;

Generating the Dashboard in a Single Prompt

Section titled “Generating the Dashboard in a Single Prompt”

What’s not in the repo is how I created the dashboard.

I didn’t write those 300 lines of SQL by hand.

Instead, I used the Shaper AI Skills. The skills teach your AI coding agent (like Claude Code, Cursor, or Codex) how to inspect the database schema, write Shaper SQL, validate queries, and preview dashboards via the Shaper CLI.

With Shaper connected to the DuckDB database from the dbt project, I gave the agent a single prompt:

I got this DBT project. Shaper is connected to the database from this project. Please generate me an overview dashboard for the data in this project. ask me for suggestions of what to show as different sections.

  1. The agent then read the dbt project and ran shaper schema to inspect the tables and columns in DuckDB.
  2. It suggested 6 sections for the dashboard and I didn’t have to adjust anything. I just replied “ok”.
  3. The agent generated Clinic Overview.dashboard.sql, ran shaper validate in the terminal to verify that all SQL queries run without errors, and opened the live dashboard in my browser using shaper preview.
Clinic Overview Dashboard Preview

Because dbt projects are well-structured and Shaper dashboards are just SQL validated via the CLI, the AI agent created a working dashboard without me having to fix anything.

And since shaper schema and shaper validate only check the schema and SQL syntax locally, the LLM never even sees your actual data.

If you want to try the demo locally, all you need is the Shaper CLI:

  1. Clone the demo repository:
    Terminal window
    git clone https://github.com/taleshape-com/model2data-shaper-demo.git
    cd model2data-shaper-demo
  2. Start Shaper with the included DuckDB file and deploy the dashboard:
    Terminal window
    shaper -d .shaperdata --duckdb healthcare_clinics.duckdb --deploy .
  3. Open http://localhost:5454/dashboards/clinic-overview in your browser.

To use the AI workflow on your own dbt project, check out the AI Agent Workflow docs. And if you need realistic test data and dbt models from a simple schema definition, definitely check out model2data on Github.

Claude Dashboards vs Shaper

Shaper is an open source dashboarding product. Now Anthropic released Claude Dashboards. What does that mean for Shaper?

The last days everyone on Data Analytics LinkedIn has been talking about how Claude Dashboards just killed the need for BI software.

This whole discussion only partially affects Shaper though: The Business Intelligence market has been crowded even two years ago when I started building Shaper.

Shaper never tried to compete with traditional BI tooling:

The problem Shaper solves:

  1. You want to share dashboards and reports with customers,
  2. but you are working with sensitive personal data that must stay in-house,
  3. and you need to be able to verify and audit results for correctness.

That’s why Shaper:

  1. focuses on embedded analytics,
  2. is fully open source and runs in your infrastructure,
  3. and defines dashboards as SQL code you store in Git.

None of these problems are solved by Claude Dashboards or the tools that came before it. I don’t expect that any healthcare company or finance org I work with to be willing to send PII to Claude or share AI generated dashboards with customers without a review process to approve the underlying analytics. Claude Dashboards looks like a great tool to query less critical data and to prototype dashboards before letting Claude translate them into Shaper SQL.


If you like to Shaper and want the ease of Claude to generate dashboards, checkout how to use our AI Agent Workflow to generate dashboards with Claude Code.

Why we open sourced Single Sign-On

We just added Single Sign-On functionality to Shaper. And we made it open source.

Single Sign-On (SSO) is the most obvious feature to separate from the main product and sell at a premium to enterprise clients.

You don’t need it to start using the product, but any bigger organization cannot do without it.

Why is SSO crucial to bigger organizations?

Section titled “Why is SSO crucial to bigger organizations?”

Obviously it’s not because large organizations care so much about UX and cannot live without the convenience of not having to type a password. Instead, it’s all about security: No weak passwords. Centralized access rights. Audit logging.

Should they care less about security? Is security something to build later on after you are already successful? I and many others don’t think so. That’s why there are websites like https://sso.tax/.

We decided to make SSO part of open source Shaper. But with a nuance:

JWT-based SSO is completely open source. You implement a single endpoint in your application and get complete control over how the user is authenticated. This is the simplest way to integrate Shaper into your existing application.

In addition to this, we provide OpenID Connect integration (OICD) and Proxy Header Auth support as part of our commercial offer. If you have an OICD provider or an internal API gateway integrated in your infrastructure, then integrating with them requires zero custom code. But investing in this infrastructure just for Shaper is definitely more complex than creating a JWT authentication endpoint.

Please reach out if you have any feedback or if you are looking for support with implementing SSO.