PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Core Concepts
Projects Components Component Settings Service Providers Deployments Domains Build Reviews Federated Apps

Federated Apps

Federated Apps are plug-and-play modules that extend your Biztraak projects with extra capabilities and make
Biztraak an extensible developer platform. They let you integrate external systems (like n8n, Elastic, or a
custom service), or add packaged functionality (like Auth, CMS, or Payments) without losing control of your infra or
governance and operational context.

Federated Apps can be distributed through the Marketplace and installed where the selected app and project workflows support it.

What is a Federated App?

A Federated App is:

  • A packaged service or frontend module that plugs into an existing project.
  • Deployable alongside your components (frontend, API, DB, etc.).
  • Distributed and versioned through the Marketplace.
  • May have its own Git repo, build pipeline, and governance metadata, depending on how it is packaged.
  • Optionally tied to APIs that can be hosted in your infra or the client’s.

Think of it as “installing an app into your project”. The app’s infrastructure, CI/CD, and governance behavior depends on its package and configuration.

Ways to Add a Federated App

Biztraak supports multiple publishing and consumption paths:

1. from an Existing Project

Select a static website from one of your projects. Ensure the root of the app is wrapped in a web component.
Mark the component as a Federated App on the component details page, and Biztraak packages it for reuse.

2. Upload a Zip of Built Assets

  • Build your frontend in any framework or language.
  • wrap you work in a web component
  • Upload the compiled .zip.
    [//]: # (- Biztraak wraps it as a Web Component compatible with Angular Module Federation.)
  • Works with Angular, React, Vue, Svelte, and more.

Link or Deploy APIs

  • Link your frontend to an existing hosted API for service-like features.
  • Or deploy a new API component alongside the app, provisioned in your infra or the client’s infra.

Runtime Behavior

Federated Apps are not iframes. They run as trusted, embeddable frontends:

  • Native Execution: load in the same JS context as the host app.
  • Controlled: installation and execution follow the app package and project access controls.
  • Composable: talk directly to other components via dependency tree.
  • Flexible: can bundle their own API or link to external services.

Examples of Federated Apps

  • CMS Integration: drop in WordPress, Ghost, or a headless CMS.
  • E-commerce: add Shopify or Stripe checkout flows.
  • Analytics: plug in BI dashboards or PostHog telemetry.
  • Messaging & Workflow: integrate Slack, Jira, or n8n.
  • Platform Services: Auth provider, email service, cache, or queue.

Why Federated Apps?

  • Faster Delivery: start from packaged integrations where available.
  • Composable: connect supported app components to project workflows.
  • Review-friendly: available operational logs and supporting context can remain attached to installed apps.
  • Customizable: fork, extend, or replace pieces of the app.
  • Marketplace participation: publishing and monetization depend on the supported account and marketplace workflow.

How to Add a Federated App

  1. Open your Project Dashboard.
  2. Select Federated Apps from the sidebar.
  3. Browse the Marketplace or upload your own.
  4. Click Install → Biztraak provisions the app and links it to your project.
  5. Configure settings (domains, secrets, scaling, API keys, etc).

Example Workflow

  • You’re building a SaaS platform.
  • Instead of coding auth from scratch, install the Auth App from the Marketplace.
  • Biztraak provisions the infra (auth DB, login service, secrets).
  • IAM Management UI added to project menu of Biztraak UI
  • Available operational and governance records can be reviewed with the installed app.
  • If needed, extend the app by linking it to a custom API hosted in your client’s infra.

Next steps

  • Projects → see how federated apps fit into projects.
  • Marketplace → explore, contribute, and monetize apps.
  • Compliance → understand how operational evidence and governance context can be attached to apps.

Federated Apps let you package embeddable features and connect them to supported project workflows.
The resulting frontend, API, infrastructure, and governance behavior depends on the app package and configuration.