Skip to content

Repositories overview

This page describes the GitHub repositories that compose the Balyze ecosystem.

All repositories are hosted under the Balyze GitHub organization. Each repository has a clearly defined responsibility to ensure clarity, scalability, and long-term maintainability.

Repository summary

Repository Purpose Audience Visibility Status
balyze Core backend & domain logic Internal dev team Private Active
balyze-website Public-facing product website Public Public Active
balyze-docs-tech Technical documentation Internal dev team Private Active
balyze-docs-user User documentation End users Public Planned
balyze-docs-api API documentation Integrators Public Planned
balyze-infra Infrastructure & deployment Internal ops Private Optional
balyze-web-front Dedicated web frontend Internal dev team Private Planned
balyze-mobile-android Android mobile application Internal dev team Private Planned
balyze-mobile-apple iOS mobile application Internal dev team Private Planned

Core product repositories

balyze

GitHub repository: Balyze/balyze

The core backend of the Balyze product.

This repository contains:

  • domain models and business rules
  • authentication and authorization
  • application workflows
  • APIs consumed by web and mobile clients
  • optional server-rendered frontend views

The balyze repository represents the source of truth of the product. If this repository is removed, the product no longer exists.

balyze-website

GitHub repository: Balyze/balyze-website

The public-facing website of Balyze.

Responsibilities:

  • product presentation
  • marketing and SEO content
  • public information about the project and organization
  • navigation hub toward the application and documentation

This repository does not contain business logic.

Documentation repositories

balyze-docs-tech

GitHub repository: Balyze/balyze-docs-tech

Technical documentation intended for contributors and maintainers.

Content includes:

  • architecture overview
  • domain rules and concepts
  • security principles
  • architectural decision records (ADRs)
  • operational references

This repository is private and versioned independently from the product.

balyze-docs-user (planned)

GitHub repository: Balyze/balyze-docs-user

End-user documentation.

Planned content:

  • usage guides
  • feature explanations
  • onboarding documentation
  • user-facing FAQs

balyze-docs-api (planned)

GitHub repository: Balyze/balyze-docs-api

Public API documentation.

Planned content:

  • API endpoints
  • authentication mechanisms
  • request and response formats
  • usage examples

Planned interfaces

The following repositories represent future interfaces built on top of the Balyze core backend.

They are not required for the ALPHA version but are part of the long-term product vision.

balyze-web-front (planned)

GitHub repository: Balyze/balyze-web-front

Dedicated web frontend consuming the Balyze API.

This repository will host a decoupled frontend application once the backend API stabilizes.

balyze-mobile-android (planned)

GitHub repository: Balyze/balyze-mobile-android

Native Android mobile application.

balyze-mobile-apple (planned)

GitHub repository: Balyze/balyze-mobile-apple

Native iOS mobile application.

Infrastructure and operations

balyze-infra (optional, future)

GitHub repository: Balyze/balyze-infra

Infrastructure and deployment-related configuration.

If created, this repository may include:

  • infrastructure-as-code
  • deployment pipelines
  • environment definitions

Operational secrets are never stored in documentation repositories.

Guiding principles

  • each repository has a single, clearly defined responsibility
  • repositories are named after their role, not their technology
  • product code, documentation, and infrastructure evolve independently
  • new repositories are created only when justified by real needs

This structure favors clarity and long-term stability over premature abstraction.

Audience note

This document is intended for:

  • maintainers
  • developers joining the project
  • contributors needing a system-level overview

It is not intended for end users.