Minyu

"Minyu is a configurable back-office information platform for modeling data, rules, and scheduling without custom development."

Minyu is a complete operational platform for organizations that need more than simple forms, basic validation, and flat data exchange. It is designed for environments where data is relational, rules are real, scheduling has constraints, integrations must be trusted, and compliance is not optional. At its core, Minyu removes the need to build and maintain large amounts of custom infrastructure for data integrity, business logic, synchronization, access control, and traceability.

What you get

Platform reliability you don’t have to engineer

Minyu runs as a fully managed, container-orchestrated system on a single trusted cloud provider, deployed across multiple availability zones with automated recovery, encrypted storage and transport, tenant isolation, and monitored backups with verified restore.

→ Read more: Platform reliability

A data model that actually reflects your domain

Minyu is built around a configurable relational data model where tables, columns, and relationships describe real-world structure and act as the single authoritative source for interfaces, APIs, validation, and data exchange.

→ Read more: Data model and schema-driven system

Real business rules, enforced everywhere

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

→ Read more: Rules and classifications

Access control defined on the data model

Read access in Minyu is defined through rule-based conditions attached to the data model itself, instead of hardcoded roles or duplicated permission logic. Access decisions can evaluate the current user, the current record, and related data across the model, and are enforced consistently across UI, search, API, and exports.

→ Read more: Read rules and access control

Scheduling driven by logic, not just calendars

Scheduling in Minyu is based on the same rule and relation model as the rest of the system, instead of a separate calendar subsystem. Availability, constraints, and multi-resource dependencies are evaluated together to determine what can actually be scheduled.

→ Read more: Scheduling and sequences

Shared schedules, applied to resources

Schedules in Minyu can be defined once and assigned to resources such as people or equipment. This makes it possible to model shared patterns —like shifts or availability schemes— consistently across many resources, while still allowing rules and constraints to be evaluated per assignment.

→ Read more: Scheduled Resources

A user interface that stays in sync with the model

User interfaces in Minyu are generated directly from the data model and rules, instead of being designed and maintained separately. When structure or logic changes, forms, lists, grids, and views update automatically to reflect the new behavior.

→ Read more: Generated user interface

Search in Minyu is relationally informed rather than purely text-based. Results and navigation paths take both values and relationships into account, allowing users to move across connected data without losing context.

→ Read more: Search and relational navigation

Imports and exports that preserve structure

Permission-aware imports and exports that support full structural mutation, including relation changes, while preserving referential integrity.

→ Read more: Imports and exports

A rule-aware GraphQL API

An auto-generated GraphQL API that respects structure, relationships, permissions, and business rules, without custom resolvers or duplicated logic.

→ Read more: API and integration

Event notifications based on meaning

Authenticated webhooks triggered by semantic changes in data and relationships, rather than by low-level row mutations alone.

→ Read more: Events and notifications

Built-in compliance and traceability

GDPR handling, immutable audit logs, and traceability are part of the core system rather than external add-ons.

→ Read more: Compliance and auditing

One system, one logic layer

Structure, rules, scheduling, imports, exports, API, notifications, and audit all execute against the same underlying model, eliminating duplicated logic and fragile synchronization.

→ Read more: Architecture and consistency

Who Minyu is for

Minyu is for organizations that need a flexible information system without the cost and risk of building a fully bespoke solution. It’s ideal for teams that have outgrown spreadsheets, struggle with poorly integrated off-the-shelf tools, or want a reliable foundation to support their data processing needs. Whether you just need a robust, configurable information backbone or a platform to integrate and extend, Minyu fits where traditional tools fall short.

Who Minyu is not for

Minyu is not intended for organizations looking for a lightweight, one-size-fits-all tool or a simple spreadsheet replacement. It is not an entry-level solution for those with very basic needs or those who want instant setup without any configuration.

It’s designed for teams who have at least one person comfortable with logical structuring and a bit of complexity, and who want a stable, configurable foundation rather than a plug-and-play tool. If your needs are very simple or you’re looking for a purely out-of-the-box solution with minimal setup, Minyu might be more than you need.

What makes Minyu different

At the center of Minyu’s design is a pragmatic principle: generalize where possible, specialize where needed.

Minyu supports real-world operational complexity that approaches bespoke systems by standardizing the parts of business systems that are common and hard to get right—structured data, rules and access control, scheduling, interfaces, and integration surfaces. This significantly reduces time to market while providing a predictable, well-tested foundation.

At the same time, Minyu does not attempt to abstract everything. Domain-specific processing and custom logic are expected to vary between organizations and are supported through clear integration points. This allows bespoke behavior where necessary without duplicating logic or undermining the system’s overall consistency.

DoDone AB

DoDone AB is the Swedish software company behind Minyu. The company focuses on building long-lived information systems for organizations that depend on correctness, structure, and reliability. DoDone AB prioritizes clarity over trends, stability over shortcuts, and long-term maintainability over quick wins, and operates fully under EU jurisdiction in compliance with European data-protection, security, and privacy regulations.

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 integration?
Contact us at .

No account or credit card required to evaluate the documentation.

Documentation · Features · Plans and pricing · Support · Legal