Skip to content

Minyu – Flexible Information Management Platform

"Minyu is a back-office information management and resource allocation platform for managing, sharing, and processing information."

Who is it for

Minyu is for organizations that need a flexible information system without the cost and risk of building a fully bespoke solution. It’s well suited for teams that have outgrown spreadsheets, struggle with poorly integrated off-the-shelf tools, or want a reliable foundation for structured data and operational processes.

It assumes at least one person who is comfortable reasoning about structure, rules, and relationships—and who values correctness and long-term stability over quick setup.

Design philosophy

Minyu is built around the five components every business information system inevitably consists of: a structured data model, rules and logic, views for interaction, integration surfaces, and domain-specific processing.

Minyu standardizes and stabilizes the first four by making them declarative, centralized, and derived from a single schema. Structure defines behavior, rules are enforced uniformly across all entry points, views are generated from data patterns rather than hardcoded screens, and integrations are always consistent with the internal model.

Domain-specific processing is intentionally kept outside the platform and connected through clean interfaces, keeping the system predictable, maintainable, and resilient as complexity grows.

flowchart TB
    %% Font sizes tuned for mobile + desktop
    classDef bigText font-size:30px;
    classDef normalText font-size:24px;

    IS[Information System]:::bigText

    IS --> DM[Structured Data]:::bigText
    IS --> RL[Rules]:::bigText
    IS --> VI[Interaction]:::bigText
    IS --> IE[Data Exchange]:::bigText
    IS --> DP[Processing]:::bigText

    subgraph MINYU[" "]
        DM --> DM_M[Declarative schema Tables, relations, constraints Single source of truth]:::normalText
        RL --> RL_M[Central rule engine Access, validation, state Evaluated everywhere]:::normalText
        VI --> VI_M[Data-driven views Forms, lists, calendars Context-preserving navigation]:::normalText
        IE --> IE_M[Model-driven integration Imports, exports, GraphQL, events]:::normalText
    end

    DP --> DP_E[External domain-specific systems Billing, payroll, logistics, custom engines]:::normalText

    style MINYU fill:#f5f7fa,stroke:#555,stroke-width:1px
    style DP_E fill:#ffffff,stroke:#999,stroke-dasharray:4 4

What do you get

Reliability you can rely on

Minyu is delivered as a fully managed platform where reliability and security are built in. Data is encrypted in transit and at rest, access is controlled through integrated authentication, and the system is designed to tolerate restarts and infrastructure events. Regular backups are performed as part of normal operation.

→ Read more: Managed Platform

A data model that represents your organization

Minyu is built on a proven, configurable relational data model. This makes it possible to represent complex real-world domains using structures that are well understood and stable over time.

→ Read more: Domain Model

Classifications as first-class system logic

Classifications provide a uniform way to assign meaning to data based on values, relationships, and logical combinations. They are continuously re-evaluated as data or time changes and form a shared foundation for access control, validation, filtering, search, and automation.

By expressing state and conditions declaratively, Minyu keeps business logic consistent, inspectable, and reusable across the entire system.

→ Read more: Classifications

Declarative, real-world business rules

Minyu supports declarative business rules that can traverse relationships and evaluate real operational conditions—who may perform an action, under what conditions, and based on which related data. The same rules are enforced consistently across the user interface and API.

→ Read more: Business Rules

Fine-grained access control

Read access in Minyu is defined using declarative rule-based conditions attached to the data model. The same logic is applied consistently across lists, search, APIs, charts, and exports.

A global optimistic or pessimistic read policy determines whether data is visible by default or must be explicitly allowed.

→ Read more: Business Rules

Constraint-based scheduling

Scheduling in Minyu is based on the same rule and relation model as the rest of the system—not a separate calendar subsystem. Availability, constraints, and multi-resource dependencies are evaluated together so that only valid time slots are presented.

→ Read more: Booking and Scheduling

Reusable schedules applied across resources

Schedules are defined once and can be assigned to multiple resources such as people, rooms, or equipment. This allows complex availability patterns—shifts, opening hours, operational windows—to be reused consistently while still being evaluated per resource.

→ Read more: Booking and Scheduling

Model-driven system behavior

System behavior and interfaces in Minyu are derived directly from the data model and rules. Forms, views, validation, and access control are generated automatically instead of being implemented and maintained separately.

This reduces time to market as models and rules evolve.

→ Read more: Model-driven System

Minyu provides a single, context-aware search across the entire system. Users do not choose where to search—results are evaluated globally, with relevance and relationships influencing how results are ranked and presented.

→ Read more: Operational Interface

A workspace designed for professional use

Minyu is designed for continuous back-office work with complex, related information. It supports parallel, side-by-side work with multiple views, inline editing, and preserved working context across sessions.

→ Read more: Operational Interface

Schema-based multi-dimensional charts

Charts in Minyu are defined directly against the data model and its relationships and evaluated under the same read rules as the rest of the system. Analytical views stay aligned with operational structure instead of being copied into reporting silos.

→ Read more: Operational Interface

Structured data exchange without breaking relationships

Imports and exports operate on full, structured models, allowing bulk updates, corrections, and migrations while preserving referential integrity—even when relationships change.

Imports are validated and reviewed before execution. Exports represent point-in-time snapshots evaluated under the requesting user’s access rights.

→ Read more: Structured Data Exchange

A rule-aware GraphQL API

Minyu exposes an automatically generated GraphQL API that mirrors the data model and relationships without custom resolvers or duplicated logic.

API access always executes in the context of an authenticated user or integration account, enforcing the same rules and constraints as interactive use.

→ Read more: API

Event notifications based on meaning

Notifications can be triggered by semantic state changes—such as a classification changing outcome—or by specific mutations across related data. External systems receive signals about what changed and why, not just that something was updated.

→ Read more: Event Notifications

Built-in compliance and traceability

Compliance and traceability are embedded directly into the data model and execution pipeline. Minyu provides structured GDPR exports, controlled anonymization or deletion, and immutable audit trails spanning full relational context.

All changes are recorded with transaction-level precision, enabling reliable audits and post-incident analysis without parallel logging systems.

→ Read more: Compliance and Traceability

What makes Minyu different

At the center of Minyu’s design is a pragmatic principle:

Generalize where possible. Specialize where needed.

Minyu standardizes the hard, recurring parts of business systems—structured data, rules, access control, scheduling, interfaces, and integrations—so organizations can move faster without sacrificing correctness or maintainability.

At the same time, domain-specific behavior is expected to vary and is supported through explicit integration points rather than hidden abstractions.

Who Minyu is not for

Minyu is not a lightweight, plug-and-play tool or a simple spreadsheet replacement. It is not designed for zero-configuration use or very basic needs.

It is intended for teams that value structure, clarity, and long-term reliability over instant setup.

Explore Minyu

The best way to understand Minyu is to see how it works in practice.

Read the documentation · View plans and pricing

Questions about fit, licensing, or integrations? Contact us at .

No account or credit card required to evaluate the documentation.