The Mahat Way
Building with Mahat App-Generator:
01
Model

Mahat App-Generator assists in creating a comprehensive business model and scope for your business needs and app.

Explore →
The process for building a software
02
Estimate

Mahat App-Generator automatically provides the work breakdown of what it can automatically build and its associated cost and timeline.

Explore →
03
Build

Mahat App-Generator automatically generates the configured application from its existing palette of business, technology and user experience patterns.

Explore →
04
Release

One click deployment of the built features for preview along with the Git enabled access to source code.

Explore →

In the context of Transactional Business Applications, Mahat can generate the following types of applications:

  • Web Apps
  • Responsive Mobile Apps
  • Flutter-based Native Containerized Mobile Apps

We classify Transactional Business Applications (TBAs) into the following categories:

  1. SaaS Business Applications
  2. Core Systems
  3. Experience Enhancers
  4. Productivity Enablers

A detailed definition and description of each category along with industry-wise examples is explained here.

Mahat is an intent and purpose driven system. It accepts and acts upon development inputs in terms of intent and purpose. It views software applications as a combination of three types of architectures: Technical, Business and User Experience Architectures. Each one of these architectures have typical patterns for each dimension within them in the context of TBAs. Mahat's Native Heuristic Engine and/or its Curated AI Integration have both been coded to interpret the user's intent and purpose in terms of each parameter within each dimension of the said architectures and suggest appropriate choices to the user. Once these choices are selected and further customized through visual configurations, upon publishing, Mahat relies on the chosen technical and UX parameters to generate the code.

Technical Architecture: Dimensions and Parameters

  1. Dimension: Architectural Decisions
    Parameters: Tenancy, Architectural Style, Pattern and Platform; Data Access and Database Choices, Access Channels etc.
  2. Dimension: Cross-Cutting Concerns
    Parameters: AAA Mechanisms, Validation and Exception Libraries, Auditing Fields, Audit Storage, Notification Channels, Caching and Storage.
  3. Dimension: Internationalization
    Parameters: Multilingual Support, Date Formats, Currency and Units.
  4. Dimension: Privacy & Security
    Parameters: Authorization Policy, Encryption, Two Factor Authorization, HTTPS Support, PIN Reminder, Auto Logoff, and Captcha Support.
  5. Dimension: Integration
    Parameters: Configuration of External API Settings, Managing Endpoints to integrate seamlessly with other systems; Setting up and managing cloud services including Azure, AWS, Git, Google Cloud and Digital Ocean for better deployment and version control; Managing User Identities, Authentication and Authorization using robust Identity Server Configuration.

Business Architecture: Dimensions and Parameters

  1. Dimension: Business Purpose and Intent
    Parameters: Business Model, Industry Vertical
  2. Dimension: Stakeholders
    Parameter: Name Values
  3. Dimension: Business Requirements
    Parameters:
    1. Business Functions.
    2. Business Processes for each Business Function.
    3. Business Objects for each Business Process.
    4. Object-Attributes for each Business Object including Business Rules and Business Logic.
    5. Business Actions to be performed on each Business Object by authorized Users.
    6. UI Patterns associated with each Business Action within any Business Object.

UX Architecture: Dimensions and Parameters

  1. Dimension: UI Elements
    Parameters: Design Frameworks, Design Standards, Icon and Component Libraries; Landing Page Settings, Accessibility and Responsiveness
  2. Dimension: Creative Assets
    Parameters: Favicons, Splash Screens, App Icons, Error Screens
  3. Dimension: Header & Body
    Parameters: Font Family, Color, Size, Background and Styles for Headers, Sub-headers, Body, Buttons etc.
  4. Dimension: Web and Mobile Navigation
    Parameters: Header and Side band background, Link color states etc for the web and mobile versions of the app.
  5. Dimension: Buttons
    Parameters: Size, Color and Link related options.

Besides automated parameter suggestions for all three architectures, Mahat also automatically writes the user stories, draws up the required Domain Models or ER diagrams based on the above process.

The code is generated based on the collaboration between the system and the user in defining the business, technology and user experience architectures and the business objects. The generated code is pushed into the code repositories for a one-click 'publish & preview' through automated CI / CD pipelines.

We use the Microsoft .net Core framework based on C# as our foundation for code generation. We support the layered architectural style with variants such as MVC based apps or API based apps or a combination of these.

Mahat vs. Low-Code Platforms: Key Differentiators

1. Co-Development: AI-Driven, End-to-End Architecture
Mahat Low-Code (OutSystems/Mendix/Power Apps)
  • Begins with application purpose (e.g., "Build a Inventory Management App") and uses platform's heuristic engine and/or AI to auto-suggest technical, business, and UX architectures.
  • Generates not just code, but also user stories, design docs, and ER diagrams.
  • Context-aware AI ensures suggestions align with business architecture, reducing manual configuration.
  • Starts with UI or workflow assembly, not business intent.
  • AI (e.g., Mendix Assist) is limited to microflows or UI snippets, not full-system architecture.
  • No automated documentation—ER diagrams, user stories must be manually created.
2. Complete Ownership & Freedom
Mahat Low-Code
  • 100% ownership of all generated assets:
    • Source code (framework-agnostic, e.g., React/.NET).
    • Design documents, requirements specs.
  • No vendor lock-in—deploy anywhere (AWS, on-prem, etc.) with no runtime licensing.
  • Proprietary output:
    • OutSystems/Mendix generate obfuscated or platform-dependent code.
    • Power Apps requires Azure/Microsoft stack.
  • Ongoing costs: Hosting/licensing mandates (e.g., Mendix Cloud, OutSystems ODC).
3. Agility: Lean, Purpose-Driven Development
Mahat Low-Code
  • Configures complexity effortlessly via intent (e.g., "inventory management system with automated stock alerts and supplier integrations").
  • Manual bridging of business/technical gaps:
    • Example: Building a "multi-tenant SaaS app" requires custom scripting for tenancy logic in Mendix/OutSystems.
  • Performance tuning (DB indexing, state management) falls on developers.
Why Mahat Wins?

Mahat eliminates low-code's trade-offs by automating architecture from intent—making it the next-gen standard for complex apps.

  • We do a functional MVP in 3 – 5 business days for the purpose of discovering the full scope of the application through extensive user/customer feedback.
  • Simple to medium sized apps (75 to 150 Business Actions) can be rolled out in 2 to 4 Weeks.
  • SaaS apps with 200 - 400 Business Actions can be rolled out in 12 to 16 weeks.
  • Support for all CI / CD best practices for versioning during each publish of the application, Collaborative branching and cloud based deployment triggers
  • Manual Save point and download of meta data for safekeeping
  • High Availability and Dynamic scalability is ensured through containerized and flexible PaaS based deployments based on customer choice on Azure, AWS or third party clouds
  • Support for Flexible scalable relational databases like SQL Server, PostgreSQL

Based on the architectural pattern chosen, API are automatically generated to ensure that the generated application can be integrable with other third party applications downstream. To get data from external system, Mahat is able to consume RESTful services.

There are no out of the box integrations with applications of the above mentioned category. Right now Mahat fully supports API based integrations. However, based on customer requirements, we are open to build or publish plugins for these as and when required.

Absolutely. We already support deployment on customer based own or third party infrastructure. Our customers are actively using the Azure IaaS, Azure PaaS, AWS IaaS, Azure Kubernetes, AWS Kubernetes, Google Cloud or Digital Ocean environments.

Source code, requirements documents, design artifacts are completely owned by the customer.

We are following the OWASP guidelines for web application development.

Sensitive data such as user passwords are encrypted on rest or in transit. RBAC is used at the action level for each business object.

Yes, we intend to do this for the first two projects for your team to get well trained on the platform. If our support is needed beyond that period, we can do it depending on the engagement model and availability of our experts.

Yes, depending on the engagement model and availability of our business technologists.

  1. You give the basic requirements for an application (from a Sales Qualified Lead or for your own product).
  2. We give you a fully functional MVP in 3 to 5 days (more than a PoC) for the purpose of discovering the full scope of the applicationa and doing accurate development estimation (team size, time and cost).
  3. You participate in the full app discovery workshop with Mahat with reference to the MVP -- 1 to 3 days (depending on app-size and your availability). Besides identifying the full scope of the core application, innovative features/aspects of the app that can give strategic business advantages are explored in this workshop.
  4. After the workshop, we will give a clear Mahat Estimate and a comparative high-code/low-code estimate that can be independently verified.

We provide a set of preconfigured UI templates that customers can choose from. For enterprise customers, depending on our engagement model, we also build specific UX patterns, plugins or assets as required for their use and later for general availability on the platform.

Customization is writing plain .net C# code or database related code based on the architectural choices. This is plain and straight forward, with no need to learn specific programming scripts or languages.

We support basic charts and graphs out of the box. Simple dashboards could be configured out of the box. Enterprise customers are free to use their existing analytics investments by connecting our transactional data source read replicas or building their specific analytical data stores.

Basic alerts are generated from the applications for default workflows configured. Event driven automation is planned in the upcoming releases of the platform.

Mahat revolutionizes software development pricing through its Mahat Business Action (MBA) model, a standardized unit to measure an application's size and cost. Check Mahat Pricing for a detailed explanation.

We are open to licensing, joint GTM models

  • Volume based discounts
  • Custom bundling of platform access, services and pre-release access, priority on roadmap features

We can support integration with Gen AI based experiences. We can also facilitate customers to move towards native interfaces with agentic ai experiences in our upcoming releases.

The platform is deployable via containers. But our on-prem hosting model might not be recommended due to high maintainability challenges and the commercial impact.

Four case studies (9 slides) can be accessed here.

Yes, our primary engagement model is way better than a PoC because what we offer is a functional Minimum Viable Product (MVP) in 3 to 5 days for the purpose of discovering the full scope of the application. We call this offer PoP: Proof of Platform.

What will be present in the MVP?
  1. The default Technology and User Experience architectural parameters are fully configured.
  2. In the Business Architecture, the stakeholders, functions, processes, representative core business objects and their actions are all fully configured and available to test.
What will not be present in the MVP?
  1. Master Business Objects and Transactional Business Objects that the already configured Business Objects are a representative of will not be present.
  2. Complex Transactional Business Objects are partially configured.
  3. Objects or their aspects that cannot be visually configured on the platform need to be custom-coded. Except simple custom coding, anything else needing more than a day will not be present in the MVP. For a mid-size application that is fit for Mahat, maxium custom coding could be up to 30% of app features.

We choose the scope of the MVP such that, with reference to it, the effort needed for the full scope of the application can be easily determined. This is because, except for complex custom coding (if necessary), all else can be quantitatively extrapolated from the MVP.

icon

Model

Mahat App-Generator assists in creating a comprehensive business model and scope for your business needs and app.

icon

Plan

Mahat App-Generator automatically provides the work breakdown of what it can automatically build and its associated cost and timeline.

icon

Build

Mahat App-Generator automatically generates the configured application from its existing palette of business, technology and user experience patterns.

icon

Release

One click deployment of the built features for preview along with the Git enabled access to source code.