Apache Superset vs Trello

Apache Superset is an open-source data-exploration and business-intelligence platform for building interactive dashboards and running ad-hoc SQL over dozens of database engines. Its REST API, documented at superset.apache.org/docs/api (confirmed live, redirecting to a 200 Swagger reference), exposes charts, dashboards, datasets, and database connections under `/api/v1/`, authenticated with a JWT access token obtained by POSTing credentials to `/api/v1/security/login` rather than a long-lived static key. Superset is self-hosted with no single Apache-run public instance, so HTTPS and CORS are configured per deployment rather than fixed by a vendor.

Trello turns Kanban-style boards, lists, and cards into a scriptable project-management primitive, letting integrations create, move, and archive cards or attach webhooks that fire on board activity. Every account gets a free API key, and requests carry that key plus a short-lived member token as query parameters rather than a full OAuth redirect — a live unauthenticated call to `/1/members/me` confirms this by returning 401 'invalid key' rather than a bearer-token challenge (auth corrected OAuth -> API Key; OAuth1.0a exists only as an alternate authorization flow for third-party apps). Trello's Power-Ups marketplace and countless third-party integrations run on this same public API, available on every pricing tier including the free plan, and CORS is wide open — both the GET and an OPTIONS preflight echo `access-control-allow-origin: *`, resolving the stored 'unknown' value to yes.