A platform where your operation lives.
Audit-ready governance. AI that respects your permissions.
Closed-scope deployment, fixed fee per company instead of per user, a dedicated environment for your data.
§01 · THE INVISIBLE COST
The real cost of an ERP is not in the license — it is in accumulated friction.
The experienced buyer recognizes the list: customization that becomes a quarterly project, audits that require SQL on the database and an Excel spreadsheet, permissions that protect on paper but nobody trusts, reports that depend on a dedicated analyst, annual negotiations with the implementation consultant.
The cost of operating an ERP accumulates in every simple question that takes longer than it should to become a reliable answer. Every opened ticket, every wait for a report, every escalation to the DBA is an invisible tax that nobody puts in the TCO spreadsheet.
Aether was designed reducing that friction in every architecture decision. That is not a slogan — it is the design criterion behind every technical decision.
The five points above are not a bug in a specific vendor. They are the consequence of a model in which ERP, governance, and data live in different layers. Aether treats them as one.
§02 · IN PRACTICE
What changes in operations, translated into observable capability
Each item below corresponds to a concrete architecture decision. We do not promise a category; we describe behavior.
- 01
New modules in days, not consulting sprints
Records, screens, reports and automations are configurable by your team. When the operation changes, the platform follows — without additional budget for every adjustment.
- 02
An audit trail an external auditor accepts
Relevant operations are recorded in a history that can't be erased. "Who changed it, who approved it, when?" is a query through the interface — not a ticket to the DBA.
- 03
Governance applied automatically
Data isolation applied in the database itself. Every new module your team creates is born with governance applied — not a separate step someone has to remember.
- 04
Native multi-unit
Branches or companies in the same group live on the same platform with real data isolation. No parallel installation per company.
- 05
Embedded operations AI
Nous answers questions in natural language about your data, respecting the permissions of the user who asked. An ordinary operator does not need to become a BI analyst to understand what is happening in the operation.
§03 · DEPLOYMENT
Three steps with closed scope and a clear exit at each one
Each step delivers a concrete artifact that your operation can use, regardless of the decision to continue.
- STEP 01
Diagnostic
Your team shows what it uses today, where it hurts, what needs to migrate. We map bottlenecks, regulatory obligations and technical debt that the new platform will inherit.
Output: closed scope for a proof of concept.
- STEP 02
POC with your real data
Reduced scope of the operation running on the platform, with your data, within the agreed timeline. The decision to continue or not is based on results — not on promises.
Output: operational evidence, not a demonstration slide.
- STEP 03
Modular deployment
Modules come in clearly sliced sprints, with functional value in each one. Your team follows along and gains autonomy as the team takes ownership of the platform.
Output: platform in homologation, not an open-ended project.
DURATION POLICY
Timeline is defined in the diagnostic, not on the page
Duration varies by scope: volume of migrated data, number of units, active fiscal obligations, maturity of the internal team. Publishing an average before having three closed cycles is guessing — and guessing wrong is costly for both sides.
Closed scope does not mean rigid. It means the agreed extension has an owner, a date, and an acceptance criterion.
§04 · COMMERCIAL STRUCTURE
Fixed fee per company, not per user
Aether charges a fixed fee per company. Scaling usage within your operation stops being an inverted incentive — expanding access does not increase the license bill.
Does your company have 50 or 500 operators? The decision to expand is about value, not about license. On our side, the conversation is about capturing operational gain — not about counting active seats month to month.
SPECIFIC VALUES
Defined with each company
Aether has no price table and no plans. The fixed fee is defined together with each company, based on an analysis of what the operation needs — scope, modules and renewal terms come out of that conversation, with enough context for both sides to decide with data, not with ranges.
- Aether — fixed fee
- Per-user model
Illustrative curve. Relative behavior, not absolute values.
Price without context becomes an objection before it becomes a decision. A qualified 30-minute conversation resolves more than a PDF price table.
§05 · NOT FOR EVERYONE
Three situations where the conversation will likely not be productive
Transparency also means knowing when to say no. If your situation is one of the three below, it is worth saving time — yours and ours.
- NOT A FIT
Looking for a commodity ERP
If your company is looking for a low entry-price ERP with no real governance requirements, there are better options on the market. Aether does not compete on top-of-funnel price.
- NOT A FIT
Expectation of deployment without internal involvement
If the expectation is "deploy in a month without the team participating", Aether is not the right choice. The platform takes shape together with those who know the operation — not despite them.
- ANOTHER PATH
White-label to resell under your brand
If the intention is to resell under your brand, the conversation happens on a different track.
Go to Partners
§06 · NEXT STEP
A 30-minute conversation with a clear output scope
Typically with the founder and a senior member of your technical team. Output: POC proposal with scope and timeline, or an honest indication that we are not the right choice for this moment.
STANDARDS MET
What the platform adheres to today
- LGPDCompatible architecture
Treatment model with specific legal basis, declared retention and operationalized data subject rights.
- Continuous audit trailIn Homologation
Sensitive events recorded with author, scope and context recoverable for external audit.
- Session-context isolationIn Homologation
Each user sees only what their context allows — closed by default.
- Segregation of dutiesIn Homologation
Authority-separation rules applied in the access profile and in the approval workflow.
- Formal certifications (ISO 27001, SOC 2)Next steps
Formal certification after the first operation stabilizes, with no set date.