m-Power's Technical Specs

m-Power doesn't ask you to adopt a proprietary stack. It assembles applications from the same open technologies your team already runs: Standard HTML and Java, using your authentication, databases, and servers. Here's the whole architecture, and how it fits together.

Get a Demo Ask an architecture question
Any browser, any device Your sign-on SAML · OAuth2 · AD YOUR SERVER · CLOUD OR ON-PREMISE FRONT END HTML CSS JavaScript Bootstrap BUSINESS LOGIC Java (JEE) Spring Framework Your custom code Third-party APIs JDBC Your existing database No migration Standard Java app server · Tomcat · Windows, Linux, or IBM i
m-Power

Follow a request through an m-Power application

m-Power generates web applications and AI tools over the databases you already run. The easiest way to see how open it is: Trace what happens when a user opens one of those applications. At every tier, you'll find technology your team already knows, and probably already runs.

Client device tier

A user opens the app on any device

m-Power applications are responsive web apps. They run in any major browser on Windows, Mac, and Linux, and adapt automatically to tablets and smartphones. Nothing to install, nothing to push to devices.

Presentation layer

The page they see is a standard web page

Front-ends are standard HTML, CSS, and JavaScript on the Bootstrap framework. The same skills behind your public website apply here: Any web designer can restyle an m-Power application, with no vendor-specific markup to learn.

Security layer

The request passes through your security, not ours

Applications come with enterprise-class security built in, and authenticate against the sign-on you already run. Users, roles, and permissions live where they live today. There's no separate identity silo to manage.

Programming layer

The business logic is standard Java on Spring

m-Power generates human-readable Java, with FreeMarker templating, plus FusionCharts and ECharts for visualization. It's code your team can read, debug, and extend, and code you can hire for on the open market.

Your own logic plugs in anywhere

Anything m-Power doesn't generate, you can attach at this tier: Call outside services, drop in routines your team already wrote, or open the code and change it directly.

Database layer

It reads and writes the database you already have

Applications connect to your existing database over JDBC, live. There's no data migration and no m-Power copy of your data. If it works with JDBC, m-Power can build over it. These are the databases our customers use most:

Runtime: App server, OS, deployment

All of it runs on infrastructure you already operate

The whole application deploys to a standard Java application server, on the operating system your team manages today, wherever your data lives. If your team can run a web server, they can run this. And if you'd rather not run one at all, we're happy to host and manage it for you as a service.

Application servers
Operating systems
Deployment

Notice what's missing from that stack

There's no proprietary runtime, no vendor-specific language, and no black box between your users and your data. The only m-Power-specific piece is the builder that assembles it all, and applications keep running even without it. That's what we mean when we say m-Power is built to be the most open low-code platform available.

Don't see your database or environment here? We probably support it. Ask us and we'll let you know.

Contact us

Because it's open, every application is yours

Building on standard technology isn't an aesthetic choice. It's what makes every application built with m-Power:

Portable

Move an application to a new server or environment with no recompile and no redevelopment. It ports as-is.

Customizable

Adapt any application to your business rules and your look and feel, down to the code level when you want it.

Free-standing

Applications run independently of m-Power. Users never need to touch the platform to use or maintain what you built.

“

m-Power owns the space on customization in terms of how well it integrates into what you're doing and how easy you make it.

Robert Reeder, CIO and VP of Technology, Henley Enterprises

Architecture questions we hear a lot

Don't see yours? Send it over. You'll get an answer from someone who works with the platform every day.

Send us a note

Page updated July 2026

What code does m-Power generate?

Standard, human-readable Java on the Spring Framework, with HTML, CSS, and JavaScript front-ends built on Bootstrap. There's no proprietary language to learn and no black box. Any Java or web developer can read, maintain, and extend what m-Power produces.

No. Applications are free-standing. They run on standard Java application servers like Tomcat, independently of the m-Power platform. Users never touch m-Power, and you can maintain applications outside of it.

Any JDBC-compatible database. The most common among our customers are Db2 on IBM i, SQL Server, Oracle, MySQL, PostgreSQL, Progress, and Snowflake. m-Power builds over your existing databases, so there's no data migration.

Yes. Customize the interface, add custom business logic, call third-party APIs, or edit the generated code directly. m-Power is built so that hitting a wall is not part of the experience.

On-premise, in your cloud (AWS, Azure, or others), or hybrid. m-Power installs on Windows Server, Linux, or IBM environments and runs over the databases you already have, wherever they live.
See it for yourself

See the architecture working over your data

We'll demo m-Power on your database and walk through the generated code with your team. Bring your hardest technical questions.

Get a Demo See how pricing works