Common questions
These answers describe how Mmosoll actually works: scoped packages, client-side cart, email-first communication, and delivery that treats security as part of the build.
Discovery workshops, a written architecture, a delivery plan with non-goals, implementation in vertical slices, automated tests on critical paths, observability, and a handover with runbooks. Optional tracks include cloud landing zones, security assessments, analytics, and applied machine learning.
The cart is stored only in your browser. Adding a package does not charge a card. When you check out, you will see: “Your order processed; one of our representatives will contact you.” A specialist then confirms scope and commercial terms by email.
Yes. We begin with a structured read: repository health, deployment path, test coverage, secrets handling, and the incidents that already happened. Then we propose a strangler or dual-run plan instead of a rewrite-for-its-own-sake.
Threat modeling, least-privilege access, secrets management, dependency review, and backup restore tests are part of delivery. Personal data handling is described in our Privacy Policy. We do not publish office addresses or phone numbers on this site; contact is through the forms and hello@mmosoll.com.
Preferred model. We pair, review, and document so capability remains after the engagement. Staff augmentation without knowledge transfer is not how we measure success.
Modern web (component frameworks and APIs), mobile clients that share contracts with the backend, cloud platforms with infrastructure as code, data warehouses, and applied ML where evaluation is possible. We choose tools against constraints, not fashion.
Subscribe from the footer or the Subscribe page after validation. Unsubscribe is always available from the footer and the dedicated Unsubscribe page. Preferences are processed on the client for this static site; a representative confirms list changes by email.
Unless a statement of work says otherwise, custom software produced for you is assigned as described in our Terms of Service. Third-party and open-source components remain under their licenses. We list those licenses in the handover pack.
