We’ve been busy. Over the last quarter we rolled out a brand‑new Dashboard package (with a slick API Access experience), tightened up authentication behavior, and made everyday dev work a little faster and nicer. We also polished consumption visuals so they read better and localise cleanly; part of our continual push for maintaining WCAG 2.1 AA standards.

A new Dashboard package, starting with API Access​

Say hello to a reusable, region‑agnostic Dashboard package. The first feature to ship in this new home is API Access.

• What is API Access: A standardised way for users to generate and manage API tokens from their account area.
• What ships today: typed hooks, ready‑to‑use UI components, and MSW handlers for realistic local dev.
• See it working, examples are wired into our app: Authenticate with a user account and navigate to the API access section on the settings page to see it in action.
• Read the docs: API Access overview and examples → /docs/architecture/apps/core/dashboard/api-access

What’s next: we’ll continue migrating more dashboard functionality out of the existing Core package and into this published package. That means less duplication, more reuse, and faster iterations for teams building on Blueprint.

Smoother sign‑in flows (and a small guard that pays off)​

Two quality‑of‑life updates for sign‑in:

• Auth responses are now deliberately quiet. We’ve redacted unnecessary error details so responses don’t give away information they shouldn’t.
• The shared Login form waits until the client is ready before enabling submit. On slow/offline connections, this prevents stray URL state from sneaking into submissions and makes the experience feel solid. We recommend adopting this pattern anywhere user input interacts with URL state e.g. Forms with a submit.

Clearer consumption visuals​

We gave consumption graphs and tables some love:

• Crisper labels across DAY/WEEK/MONTH/YEAR ranges (better readability and screen‑reader output)
• Customisable date‑range formats for both the graph and the table
• Statistics card totals now align with consumption chart values (rounding/formatting fix)

Developer experience​

We're investing in making everyday tasks feel lighter. One example: a typed React Query mutation helper for calling custom API routes is now part of @krakentech/blueprint-api.

The useApiRouteMutation hook streamlines HTTP requests to custom API endpoints with full TypeScript support, automatic error handling through the existing Kraken error system, and React Query integration for state management. Whether you're calling /api/users/profile or /api/org/initialize-user, the hook handles JSON serialization, error boundaries, and provides type-safe request/response handling out of the box.

Read the docs: API reference and examples → /docs/architecture/packages/krakentech-blueprint-api/api-reference#useapiroutemutation

We also tuned our CircleCI setup to be faster and cheaper without losing signal. In practice: we run only what changed (dynamic path‑filtering), drive E2E with Playwright workers instead of CircleCI sharding, and spin up a production build with integrated server management so tests mirror reality. We standardised Node and Playwright executors, fixed pnpm caching, employ turbo caching and omitted publishing videos in failure reports to utilise traces for debugging. Result over the last 30 days: an 87% reduction in credits used and a 79% drop in total workflow duration.

Up next​

• More Dashboard surfaces: migrate additional Core dashboard features into the published Dashboard package

Thanks for reading​

Questions or want a pairing session? Ping the Blueprint channel (#ext-oe-blueprint-feedback) — we’re happy to help demonstrating how to wire things up or assist with migrating existing features.

Season's greetings from the Blueprint team! 🎄

Hi there folks, we wanted to report on the progress of our packages as we roll them out to more customers!

Hello folks, a quick update from us on how our package journey is going, plus other things we've been working on!

Hello everyone, and thank you for taking the time to check out our latest update. Since our last post, we’ve been working to share more of the (Javascript) collateral we’ve built up in our Blueprint project as npm packages, so people can pick and choose the utilities that they need in their projects, as well as benefit from updates we make after their project has been forked.

Hello and welcome back to the Blueprint blog! It's been a very exciting month for the team - we've released our first package into the @krakentech organisation - @krakentech/blueprint-utils. This means we can start sharing more than just API examples and UI demos, we can start to export real utilities that make it even easier to "Blueprint" features in your existing apps.

Internally we've reached another key milestone - we've reworked our authentication approach to use API routes and middleware, which we are aiming to add to our new @krakentech/blueprint-utils package. To learn more about the approach to managing authentication, please see our Authentication Guide. We're aiming to offer an upgrade path to previous Blueprint projects to adopt more of our new stack, and the features that come with it, without having to do a full replacement of Apollo Client. Stay tuned for future updates!

A big hello to any readers of our new Blueprint blog! We'll use this as a way to notify people of updates to our docs, new releases to our packages and anything else we think may be helpful. Stay tuned!