01
Scalable SaaS architecture
With multiple customers, roles, subscriptions and integrations, the data model, the audit log and permission management are part of the plan from the first release.
Platforms and operations
A platform only serves the business if growth doesn't make it fragile. We deliver scalable SaaS, ecommerce built for business buyers, and predictable operations — all from one place.
Specification, measurable acceptance criteria, and regular demonstrations are part of delivery, just like the code.
01
With multiple customers, roles, subscriptions and integrations, the data model, the audit log and permission management are part of the plan from the first release.
02
Custom price lists, contract-based partner permissions, approval workflows and connections to enterprise systems: B2B purchasing is not a consumer cart in a new colour.
03
Monitoring, incident alerts, security patches and plannable development capacity. The SLA makes response times, responsibilities and the rhythm of communication explicit.
SzoftMűhely commitment
At the start of the project we agree the scope and the handover conditions. The code and the infrastructure are fully yours, and the team remains directly reachable.
Yes, after a technical assessment. The aim is to make dependencies, risks and priorities visible before we commit to an SLA.
The agreed monthly allowance can cover bug fixes, updates, monitoring and smaller improvements, with a transparent task list.
The committed response time follows the criticality of the system and the maintenance agreement; the support process is documented at handover.
Write a few sentences about the situation. We reply within one business day and suggest a 30-minute call — no obligation.