Build the operational systems your team keeps trying to assemble from spreadsheets, boards, inboxes, and custom scripts, with cloud and self-hosted deployment, portable data, and room for real business logic.
Start in the cloud. Self-host when control matters. Your data stays portable.
01
01Why Moltaro
Operations apps that stay useful as the work gets more connected.
01
Model the work, not a template
Define the records, forms, fields, relations and views your operation actually needs, then keep adapting them as the process changes.
02
Boards, maps, and reports stay connected
Move work through boards, see locations, zones, heatmaps and coverage on maps, and report on the same records instead of rebuilding the picture from side trackers.
03
Cloud or self-hosted
Start in the cloud for a faster pilot, or self-host when policy, contracts, local debugging, or infrastructure ownership matter more.
04
Portable relational data
Operational data lives in a standard relational model you can inspect, export, integrate, and take with you.
05
Real business logic when no-code ends
Use C# logic, APIs, webhooks, triggers, and scheduled jobs when the process needs implementation depth beyond configuration.
06
Governance is the trust layer
Roles, field access, responsibility, audit history, and deployment control keep the operation explainable as more people and records depend on it.
02
02Beyond basic app builders
Not just screens over a database.
Basic app builders can put forms and tables on top of data sources. Moltaro gives each operational record its own data, process state, responsibility, access rules, history, boards, maps, reports, and extension points.
01
A record has a life
Data, status, ownership, comments, files, audit history, and relationships stay attached to the same business object.
02
Process belongs to the record
Move work through boards, stages, handoffs, and location-aware routing without splitting the same case into disconnected copies.
03
Reports see the real operation
Dashboards and exports read from the same operational model instead of reconstructing the truth from side trackers.
04
Code is there when configuration ends
Use C# logic, APIs, triggers, and scheduled jobs when the process becomes too specific for no-code rules.
05
Governance is not a bolt-on
Roles, field access, responsibility, audit, and deployment control are part of the model, not an afterthought.
03
03Who it's for
Start from the entry point that matches how the work breaks today.
Moltaro fits when scattered tools still hold the operation together, but reporting, ownership, permissions, and long-term change need one product model.
01
Solution builders and consultants
Build client or department apps with UI, structured data, access control, workflow and real C# business logic on one platform.
Fits when a serious operations app should be delivered faster without becoming a one-off custom codebase.02
Teams replacing scattered operational tools
Work already runs across spreadsheets, boards, inboxes and side trackers, but ownership, status and reporting no longer line up.
Fits when disconnected tools need to become one operational record model with workflow, audit and reporting.03
Location-aware field and aid operations
Work starts from addresses, service locations, field assets, territories, visits, delivery points or aid distribution sites and has to reach the right team.
Fits when maps, zones, heatmaps and geography should drive responsibility, board context, access scope, reporting and audit.04
Operations and back-office teams
A back-office system that needs its own business objects, roles, audit, workflow, notifications, C# logic, API, webhooks and portable data.
Fits when the operation needs its own durable model, not a thin editor over someone else's application database.
04
04Governed record
The record your team cares about stays at the center.
A governed record can accumulate data, process presences, responsibility slots, inherited child responsibility, audit, map position, reports and integration events. Boards are one way to work with it, not the place where the object disappears. In the platform, the model is an Entity and each record is an Entity Instance.
The audit trail is not an afterthought. It is the proof layer for who changed data, moved work, accepted responsibility, triggered automation or resolved a blocker.
01
Model the object
Define the real thing the business cares about: request, person, asset, shipment, case, location, order, product, entitlement or service point.
02
Give it surfaces
Create list, detail, form, map, board and dashboard surfaces so different users can work with the same record in the right context.
03
Govern the movement
Add access, responsibility slots, team assignments, inherited child access, status movement, notifications, C# logic, API hooks and audit so the process can run without losing control.
Govern responsibility, access and ownership as one model.
Moltaro ties record responsibility, team and committee assignments, field visibility, inherited child access, Boards item/status responsibility, GEO-based assignment, audit, and deployment ownership into one explainable platform story.
Responsibility and access console: record roles, inherited child access, Boards responsibility, GEO assignment, field visibility, and history in one administration surface.
01
Responsibility is first-class
Model owner, accountable, assignee and reviewer slots per entity, then assign users or teams to the concrete record where they are responsible.
02
Hierarchy without leakage
Contained child records can inherit mapped responsibility from the parent, while ordinary references stay independently governed so access does not spread by accident.
03
Cross-module responsibility
Boards can use item responsible and status responsible subjects; GEO can route work to the right responsible team; reports and inbox signals keep that accountability visible.
04
Identity verifies; Moltaro authorizes
External identity can prove who the user is, while each installation still owns local users, roles, responsibility, field rules, audit behavior and runtime data.
Turn location into responsibility, routing, and reporting.
Moltaro GEO connects address and coordinate fields, Geo Zones, heatmaps, map layers, and geo-based assignment so teams can see where work happens and route it to the right people.
Zones & territoriesHeatmaps & classificationPermission-aware map layersTeam assignment by location
Operational map showing heatmaps, zones, work demand, filtered records, and the teams responsible for each area.
01
See work, demand, and coverage on a map
Requests, assets, visits, cases, service points, inspections, beneficiaries, delivery points or distribution sites can appear as markers, aggregates, zones or heatmaps.
02
Route work by territory
Addresses and coordinates can select the responsible team, board context, access scope, SLA path and audit explanation before work is handed off.
03
Report by location without a side tracker
Maps and reports read from the same operational records, so delivery, service, coverage or field work stays tied to audit and permissions.
Move work through stages without splitting the record.
Boards add a controlled process over the same business object: stages, responsible people and teams, due dates, history, and location-aware routing while the record stays the single source of truth.
A board item carries process state and history; the underlying record keeps its own data, access rules, and change history.
01
One record, many boards
The same object can appear on several boards or come back for another pass without becoming a disconnected copy.
02
Responsible people and teams
Assign each item to the person or team handling it, and give each stage the team responsible for moving work forward. People can act because they are responsible, without opening the whole board to everyone.
03
Kanban or cycles
Run a continuous Kanban board or planning cycles with rollover, scoped to the same permissions, child blockers and responsibility model.
04
Responsibility by location
Use the work's location to route it to the team responsible for that area, while every handoff stays tied to the same record.
Know exactly who may use a license, membership or service.
Entitlement Operations turns access rules into operational records: define a model and plan, grant it to a person, organization or family, then answer whether a beneficiary may use a specific resource. It is not a billing system.
Start with one real object, then build the system around it.
Choose the record your team cannot afford to lose, add the process around it, then extend with roles, audit, reports, maps, C# logic and integrations.
01
Choose the operational pain
Low-code internal system, spreadsheet replacement, geo operations, lifecycle operations, service requests or another concrete scenario.
02
Define the core object
Name the record that must not be duplicated or lost: case, asset, beneficiary, address, request, order, unit, grant, visit or contract.
03
Add process and control
Use boards, rules, responsibility slots, responsibility groups, permissions, inherited child access, notifications, reports and audit to make daily work accountable.
04
Extend where needed
Use C# logic, API, webhooks, CRON functions and direct database integration when the process needs real implementation depth.
Choose who owns keys, SMTP, database backups, capacity, and updates.
Price is not the first decision. The real split is whether Moltaro can use provider backup and scaling mechanics, or your team maintains every credential, restore plan, and hardware move.
Managed App
Moltaro operates the application and its service dependencies.
Best when you want production without owning provider setup, Docker hosts, database backup baseline, capacity changes, Google Maps key rotation, SMTP sender setup, or upgrade runbooks from day one.
Starts from $99/month while DigitalOcean is the primary planned provider.
Portal-managed install, update progress, URLs, version metadata, protected secrets, and support workflow.
Less direct infrastructure control, but fewer operational duties around keys, mail delivery, database backups, capacity growth, and updates.
Self-hosted
You run the stack and every external service.
Best when contracts, security policy, local debugging, or infrastructure ownership matter more than having Moltaro operate the environment.
Free perpetual local license, with paid unlimited and maintenance options.
Your team owns Docker, PostgreSQL, database backups, files, full-text data, DataProtection keys, DNS, SMTP, Google Maps API key, hardware capacity, and upgrades.
More control and easier local debugging, but service setup, restore testing, and server moves are on you.
Both paths run the same Moltaro product. The difference is who carries the operational checklist after installation.
