It runs on your servers.
Here’s exactly what
that means.
Miraxtech deploys inside your perimeter: your infrastructure, your access controls, your audit regime. This page describes what gets installed, where it runs, and what we can and cannot see.
Every product on this page runs on infrastructure you own and administer. Nothing on it describes a hosted service.
Every product, its own footprint
Miraxtech products are separate platforms, not one suite install. Each has its own footprint, and all of them sit inside your perimeter. You deploy only what you run.
Integration Gateway
your serversIntegration middleware. Connectors out to your providers and platforms, running under credentials you hold, landing data in storage you control.
Affiliate Payments
your Business CentralA native extension installed into the Dynamics 365 Business Central instance you already run. Nothing outside the ERP.
PSP Fees Reconciliation
your SQL ServerA data warehouse built on Miraxtech templates, plus the recalculation engine, on your Microsoft SQL Server.
Traffic & Conversion
your Power BIPower BI dashboards and report templates, reading a warehouse built on Miraxtech templates.
Separate platforms, separate installs · you deploy only what you run
Outside your perimeter. No hosted copy of your data, and no way into your systems except access you open, scope and close.
What we can see: nothing in production
Transaction data never leaves your infrastructure. There is no Miraxtech cloud, no telemetry stream carrying your numbers out, and no copy of your data on our side to be breached, subpoenaed or leaked.
| Data | Where it lives | Reaches Miraxtech |
|---|---|---|
| Transaction and settlement records | Your SQL Server warehouse | No |
| Affiliate balances and payouts | Your Business Central instance | No |
| Provider and platform credentials | Your credential store | No |
| Contract fee terms | Your systems | No |
| Reports and dashboards | Your Power BI | No |
There is no Miraxtech cloud for any of it to be copied into.
Access for support
Access for support exists on your terms: you grant it, you scope it, you revoke it — under the same controls you apply to any contractor touching your systems.
On-premise is the security model
Your existing data-residency requirements, retention rules and access policies apply unchanged — because the system lives where those policies already apply.
Data residency
Whatever your residency requirements are, they already apply to these servers. Installing here does not move data across a border, because it does not move data at all.
Retention
Your retention rules apply unchanged. The records the products read and write sit in stores your policy already covers.
Access control
Your directory, your roles, your logging, your review cycle. The system sits behind the controls you already operate rather than beside them.
Custody
There is none to assess. We are not a processor holding your records somewhere else; the records never leave the place they were already kept.
There is no new trust relationship to establish and no vendor risk assessment for data custody — because there is no data custody.
From provider list to production
Four phases. The first one costs you a list and an email.
Scoping
You send your setup — ERP, platform, providers, payout models. We reply in writing: what is covered, what needs building, what the effort looks like.
Warehouse and Gateway stand up
Deployed on your infrastructure, connected to your first providers.
Modules install and map
The Business Central add-on installs; mapping aligns to your chart of accounts and your payout models.
Parallel run, then cutover
The system runs alongside your existing process until the numbers agree — then it becomes the process.
A sequence, not a schedule. Dates go against these steps at scoping, once the provider list is known.
Support from
the people who wrote it
Escalation goes to the product team that built the module. There is no service tier standing between you and them.
- 24/7 cover, through your channel of choice
- 36 engineers across the product teams — the same teams that write the code
- Business Central version upgrades don’t break the integration. That is an explicit design constraint, not a hope
Put this page in front of your infrastructure team
Then send us the questions they still have — those are usually the interesting ones.