Open-source products

Open-source software can be the foundation of a product instead of a repository customers must operate themselves.

MIOSA can host the application layer, data services, customer environments, updates, and public or private access.

Self-hostable now External services may be required

Product directions

Private AI workspace

Package an open-source chat or knowledge interface with customer-specific data and connected model endpoints.

Automation cloud

Offer a managed workflow automation product with templates, credentials, execution history, and support.

Analytics product

Turn an open-source dashboard or business intelligence system into an opinionated vertical service.

Internal developer portal

Package source control, deployment, service catalog, and environment workflows for engineering teams.

Knowledge platform

Host search, document processing, collaboration, and agent workflows around private customer content.

Customer support suite

Combine an open-source inbox or help desk with agent assistance and industry-specific workflows.

Media management

Provide a managed asset library, processing pipeline, search, and creative automation experience.

Security operations tool

Operate open-source scanning or monitoring software with a customer portal and evidence workflow.

Deployment models

flowchart TB
  Source["Open-source project"] --> Package["MIOSA application package"]
  Package --> Shared["Shared multi-tenant service"]
  Package --> Dedicated["Dedicated customer deployment"]
  Package --> Computer["Persistent customer computer"]
  Shared --> Data["Managed customer data"]
  Dedicated --> Data
  Computer --> Data
  Data --> Domain["Branded domain and access"]

Shared application

Run one application with tenant-aware data boundaries.

This is efficient when the upstream software supports strong multi-tenancy.

Dedicated deployment

Run an isolated application release for each customer or regulated boundary.

This simplifies customization and failure isolation but requires fleet-aware updates.

Persistent computer

Run software in a full desktop environment when it expects a graphical session, local browser, or native application.

Package the operational value

Customers pay for outcomes around the software:

• Provisioning and upgrades.
• Backups and recovery.
• Secure customer isolation.
• Integrations and model access.
• Opinionated workflows and templates.
• Monitoring and incident response.
• Support and migration.
• Branded interfaces and domains.

Update safely

Build a new immutable candidate before changing production.

Verify its configuration, data compatibility, health, route, and required capabilities.

Promote the exact candidate only after those checks pass.

Keep the prior release available for rollback.

For dedicated customer deployments, use a rollout controller rather than manually visiting every instance.

Check the license

Confirm that the project license permits your intended distribution, modification, hosting, and branding model. Preserve required notices and source obligations.

Useful open-source foundations

Potential foundations include AI interfaces, workflow engines, knowledge systems, analytics tools, support platforms, developer portals, data services, and media applications.

Choose a project based on maintainability, license, data model, upgrade behavior, health checks, and whether it supports the isolation model your product needs.

Publishing and releases Package a candidate release, verify it, promote it, and preserve rollback.