Main content
EnglishRomână
Contact
EnglishRomână

SaaS and web platforms, designed, built and run

SaaS and web platform development for products with several kinds of users: payments, e-signature and accounting built in, plus the admin tools the staff work in.

Project briefWeb platform case studies
FIG. 1Mozar architectureIn production
Mozar architecture: an entrepreneur app, an accountant app, an auditor app, an admin app and a CRM share one backend, where access rules decide who sees what. The backend connects card payments, e-signature, accounting platforms, the company registry and ad conversions. An AI agent can operate the admin, and nothing changes until a person confirms.Web appsOne per audienceDatabaseAccess rulesIntegrationsPayments, e-signature

Integrations shipped: payments, e-signature, accounting

Integrations are built to recover from errors, so a network glitch cannot charge a card twice or sign a document twice.

  • Card payments
    What was built: Card checkout and refunds built into the order flow
    Project: Mozar
  • E-signature
    What was built: Reports generated, then signed electronically
    Project: Mozar
  • Accounting platforms
    What was built: Accounting data imported per firm, companies matched automatically
    Project: Mozar
  • Company registry
    What was built: Company details filled in from the French business registry
    Project: Mozar
  • E-invoicing
    What was built: Invoices and payment status synced from a Romanian e-invoicing platform
    Project: Renovation contractor (NDA)
  • Transactional email
    What was built: Ticket and booking emails that always reach the visitor
    Project: Muzeul Baia
  • Ad conversions
    What was built: Ad conversions reported without slowing checkout
    Project: Mozar

SaaS, operations and training platforms

Multi-role SaaS

Mozar

Entrepreneurs, accountants, auditors and admins, each with an app, on one database.

Every status email, sent by the platform

Status emails nobody writes by hand

Mozar case study
FIG. 2One mission, four rolesDemo data

  • Entrepreneur

    Mozar online quote questionnaire, step 2 of 4, for a share contribution mission: answered questions on holding creation, number of companies, SIREN, contribution value and revenue.

  • Accountant

    Mozar professional dashboard for one mission: required documents grouped into identity, legal and financial, one document flagged for revision with the auditor's note, mission progress at 50 percent and a discussion thread with the auditor.

  • Statutory auditor

    Mozar auditor view of the same mission: each uploaded document with Approve and Request a correction buttons, approved badges, a revision note, a 6 of 10 documents processed counter and the shared discussion.

  • Admin

    Mozar admin pricing screen for the share contribution mission: base price, price per point, multi-entity discount, and a live preview estimating 1 740 euros for two companies with 20 percent off the second.

Operations software for one business

Rarău Rental

A ski rental counter off paper, every scan priced.

40%

More clients served in the same time

Inventory, booking, self check-in

Rarău Rental case study
FIG. 3Counter and check-inDemo data
Operator console with draft rental sheet 260927-0015 for a demo customer: seven scanned items for three days and a price panel with two ski packages, 375 RON to collect and 165 RON saved against individual rates.
Rarău Rental check-in on a phone, step 1 of 3: a photo of an ID card clearly marked SPECIMEN fills the front-side slot, with a Continue button below.

Training and compliance platforms

OpenTest

Mandatory safety (SSM) and fire (PSI) training online, down to the statutory record.

A whole company added in one upload

Employees added in one upload

Project notes

Its owner has used OpenTest to win training contracts with large employers.

OpenTest case study
FIG. 4One test, two languagesDemo data
OpenTest on a phone, question 4 of 6 of the fire prevention test in Romanian: how to leave the building during an evacuation. The answer about taking the stairs along the marked route is selected in green; a progress bar and the line Ultima salvare: 22:44:02 sit under the card.
The same attempt after switching to English: question 2 of 6 asks which extinguisher to use on live electrical equipment, with Carbon dioxide (CO2) and Dry powder still selected from the Romanian session, and the last save time under the card.

Access and GDPR rules, enforced once for every app

Access rules, audit trails and GDPR erasure are designed in from day one, and every app follows them.

The same controls answer an EU customer's NIS2 questionnaire: NIS2 for software suppliers.

Controls we build in

Access rules per role
Each role sees only its own data, and automated tests check it on every release.
Every platform
Multi-factor sign-in and an audit trail
Staff sign in with a second factor, and every sensitive change leaves a record.
Every platform
GDPR erasure and retention
Personal data has a documented retention period and a clean erasure path.
Every platform
An AI agent that changes nothing unconfirmed
The agent proposes a change, and a person approves it before anything is saved.
Every platform

Readiness assessments and gap analysis sit under cybersecurity and NIS2.

FIG. 5Where the controls sitComposite
A composite view of the controls shipped across projects: multi-factor sign-in for staff, abuse protection, access rules per role, an audit trail, GDPR erasure, and an AI agent that changes nothing until a person confirms.Staff appsServerDatabaseAI agentMulti-factor sign-inAbuse protectionAccess rulesAudit trailGDPR erasurePerson confirms

Legacy migration, and users keep their passwords

FIG. 6Legacy migration, rerunnable
Legacy migration: the old system is left untouched, every run is rehearsed before it counts, records keep their links, and a second run updates data instead of duplicating it. Users keep their passwords, so nobody resets one.ReadUpdateOld systemLeft untouchedMigration toolRehearsed firstLinked recordsKept intactNew platformNo duplicates

The four migration rules

The old system stays untouched
Data is copied out, never changed at the source.
Rehearsal first
Every run reports what it would change before anything changes.
Links kept, no duplicates
Records keep their links, and running the migration again updates data instead of duplicating it.
A runbook that starts from failure
What to check, when to stop and how to roll back, written before cutover day.

Existing passwords kept working, so no Mozar user had to reset one at cutover.

SaaS and web platform FAQ

Cost of a SaaS platform or MVP

An MVP is priced from a written scope: which audiences get an app, which integrations are live on day one and which can wait. The leanest first release carries one audience end to end. The build is then priced per stage.

Security and GDPR in the platforms we build

Security is designed in from day one: access rules per role, secure sign-in for staff, a record of sensitive changes and a documented retention and erasure path for personal data.

NIS2 for software suppliers

Payments, e-signature and accounting integrations

All three run in production on Mozar: card checkout and refunds, e-signature on the final report, and accounting platforms connected per accounting firm. The platform uses each provider's public API; none of these integrations is a partnership.

Back office and admin tools

Every platform ships with the back office its staff need. Mozar's admins configure mission types, documents and prices without a deploy; Muzeul Baia's staff run tickets, exhibits and reports from one Romanian admin panel with separate roles.

Muzeul Baia case study

A first release, scoped in writing

A few lines on the users and the systems to connect are enough to start.

Project brief
Case studies
Email
contact@elastoapps.com
Studio
Cluj-Napoca, Romania, EU