All your questions
about WakaStart.
With real answers.

WakaStart is a French industrial software forge specialising in building and migrating certifiable B2B SaaS. Born from the JDS Conseil group (founded in 2004 in La Chevrolière), WakaStart distils 25 years of industrial software development expertise into a proprietary method called Cybercoding. WakaStart enables startups, scale-ups and software vendors to launch or overhaul a B2B SaaS in a matter of weeks — with a Secure-by-Design architecture, 100% sovereign hosting on OVH France, and ISO 27001, NIS2, GDPR and HDS rules built natively into every line of code. Unlike a traditional development agency, WakaStart commits to a fixed fee, a guaranteed timeline, and code delivered ready for ISO 27001 certification. The WakaStart Run team then handles maintenance, updates and round-the-clock monitoring of the delivered SaaS.

Cybercoding is WakaStart's proprietary method — a forge of AI agents that generates code while systematically embedding ISO 27001 and NIS2 security rules and enterprise architecture best practices, leaving no room for developer improvisation. Unlike Vibe Coding tools such as bolt.new or Lovable, which generate functional code quickly but without security rules, Cybercoding enforces: consistent, complete application generation in a single pass (no patching), a SAST/DAST pipeline that blocks any build containing a critical vulnerability, native multi-tenant isolation via PostgreSQL Row-Level Security, identity management through Keycloak IAM with enterprise RBAC, and four strictly isolated ISO-mirror environments (Dev, Staging, UAT, Production). In practice, Cybercoding cuts time-to-market by a factor of 12 compared with traditional development, and cost by a factor of 8 — while delivering code that is directly certifiable to ISO 27001.

The fundamental difference is between a prototype and an industrial product. A Vibe Coding tool generates code fast — typically in 6 months for a functional V1 costing around €150,000 — but that code will be rejected by any security audit. The reasons: secrets stored in plain text, no NIS2-compliant audit logs, non-existent or fragile multi-tenant isolation, default deployment on US clouds (Vercel, Supabase, AWS) subject to the Cloud Act, and no ISO 27001 technical documentation. WakaStart generates an enterprise-grade SaaS in 30 days: sovereign OVH France infrastructure, Keycloak IAM with RBAC, secrets stored in Vault, per-tenant RLS partitioning, a SAST/DAST pipeline, automatically generated PAS/PAQ/BCP/DRP documentation, and a file ready for a COFRAC ISO 27001 audit. The WakaStart package starts at €30,000 excl. VAT — 5 times cheaper than Vibe Coding once the post-audit rewrite is factored in, and 16 times faster.

No. WakaStart is not a development agency and does not bill by the day. The difference is fundamental. A development agency sells you person-days: day rate × estimated number of days = budget. If the project takes longer, you pay more. The outcome depends on the quality of the developers assigned to your project. WakaStart commits to an outcome — a fixed fee, a guaranteed timeline, and a deliverable that meets industrial standards of quality and security. If WakaStart underestimated the workload, that's WakaStart's problem, not yours. It's the difference between buying hours of work and buying a guaranteed result. Moreover, WakaStart doesn't deliver and disappear: the Run team handles maintenance, updates and round-the-clock monitoring of the delivered SaaS, for a predictable monthly fee.

Wakanalytics is the free technical audit offered by WakaStart within 48 hours. It's the first step of every WakaStart project — and it's free, confidential and comes with no obligation. Wakanalytics includes three deliverables: a security vulnerability map (detection and severity classification — multi-tenant isolation, access rights management, secret exposure, OWASP compliance), a quality and technical debt audit (identifying architectural weak points, outdated dependencies, and blockers to ISO 27001 certification), and a precise budget estimate built on the reality of your code. Wakanalytics isn't a contact form — it's a genuine code analysis carried out by our Lead Developer and our CISO. To get started, all it takes is a 5-minute form and a 30-minute scoping call. The report arrives within 48 hours, followed by a 30-minute debrief to discuss the findings.

WakaStart is designed for B2B SaaS — professional applications with multiple users, distinct clients (multi-tenant), security requirements and regulatory compliance. WakaStart is particularly well suited to startups launching their first SaaS, scale-ups looking to overhaul an existing SaaS, on-premise software vendors moving to cloud SaaS, and large enterprises modernising their legacy application estate. WakaStart is not, however, suited to simple consumer apps, e-commerce sites without multi-tenant complexity, landing-page or CMS-type projects, or single-user applications without B2B business logic. If you're unsure whether WakaStart is right for your project, the free Wakanalytics is designed precisely to answer that question — within 48 hours, with no obligation.

No. WakaStart works with your teams, not instead of them. For overhaul or modernisation projects, your developers take an active part in the reverse-engineering phase and validate the specifications — their product knowledge is irreplaceable. After delivery, they upskill on the WakaStart stack (Nest.js, Kubernetes, Keycloak, GitOps) and move from constant firefighting maintenance to building business value. For new builds (startups), WakaStart can develop the entire product without an existing in-house team. In every case, WakaStart avoids long-term lock-in: the source code is standard TypeScript/Nest.js, maintainable by any development team. Your teams remain in control of their product.

Yes. WakaStart is a French company, born from the JDS Conseil group founded in 2004 in La Chevrolière (Loire-Atlantique). All infrastructure is hosted in France on OVH Cloud. The teams (Lead Developer, CISO, Run team) are based in France. This isn't a marketing detail — it has concrete regulatory implications: your clients' data remains subject to French and European law, not the US Cloud Act. For HDS (health data) or sensitive projects, this is an absolute requirement. WakaStart is recognised as one of the players in French digital sovereignty.

Building a B2B SaaS in France in 2026 involves several simultaneous dimensions: technical, regulatory and commercial. On the technical side, a professional B2B SaaS must include multi-tenant architecture (isolating each client's data), robust IAM (identity and access management, SSO), scalable infrastructure on a sovereign cloud, and a secure CI/CD pipeline. On the regulatory side, NIS2 compliance is now mandatory for B2B digital service providers, and GDPR compliance is a legal obligation. If your SaaS processes health data, HDS certification is legally required. ISO 27001 certification is demanded by almost all large enterprises in their tenders. Financially, traditional development (through an IT services firm) costs €150,000 to €500,000 and takes 12 to 18 months. WakaStart lets you launch a certifiable ISO 27001 B2B SaaS in 30 days from €30,000 excl. VAT, payable in instalments with no bank loan from €2,000/month.

WakaStart guarantees a functional V1 in production within 30 days for a Startup profile, and 3 to 4 months for a full overhaul of an existing Scale-up SaaS. For a startup, this breaks down as: Wakanalytics (48h, analysis and scoping), Week 1 (functional and security specifications validated), Weeks 2–4 (generation and deployment on OVH France), and Month 2 to finalise ISO 27001 preparation if that option is activated. This timeline is contractually guaranteed — not a commercial target. The condition is that the specifications are validated by the end of Week 1. If Wakanalytics reveals your project is more complex than expected, WakaStart will tell you before signature, with a revised timeline.

The WakaStart process follows 5 steps: (1) Wakanalytics (free, 48h) — analysis of your requirements or existing code, delivering a report with a fixed budget and guaranteed timeline; (2) Functional and Security Specifications (FSS) — the AI analyses your brief and produces a full FSS document, submitted for CISO review and validated by you; (3) Atomic generation — the AI agent forge generates the application in TypeScript/Nest.js as a single block, natively embedding all security rules; (4) SAST/DAST pipeline — every build is audited, with zero critical vulnerabilities permitted in production; (5) Deployment on OVH France — your SaaS goes live on preconfigured infrastructure, with Grafana monitoring and round-the-clock Run on-call support.

An 8- to 15-page Word document describing your business needs is enough to kick off the Wakanalytics. You don't need a 150-page technical specification — producing that is precisely the job of WakaStart's Phase 1. What WakaStart needs is: your product vision (what it's for, who the users are, the main features), your target market (B2B, sector, client size), your regulatory constraints (health data, finance, defence?), and your budget and timeline. Cybercoding's cognitive reverse-engineering turns your raw business brief into complete technical and security specifications — including ISO 27001 and NIS2 requirements tailored to your context.

A WakaStart V1 delivered in 30 days includes: the complete business application with all features validated in week 1, enterprise authentication (Keycloak IAM — SSO with Google, Microsoft, Apple, Active Directory, SAML, MFA), native multi-tenancy with per-client RLS partitioning, a responsive interface with configurable white-labelling (colours, logo, domain), i18n internationalisation with automatic translation, automated CI/CD with zero-downtime deployments, OVH France infrastructure (Kubernetes, Grafana monitoring, AES-256 backups twice daily), and complete technical documentation (PAS, PAQ, BCP, DRP). What is not in the V1 by default but is available as an option: the WAKA-SIGN module (eIDAS signature), WAKA-DOC (document management), WAKA-FACTURE (Factur-X invoicing), WAKA-SCRIBE (AI transcription), and ISO 27001 preparation.

Yes. Cybercoding generates bespoke code from your business specifications — not generic templates. WakaStart has delivered SaaS products across very different sectors: equestrian centre management (Horsees), B2B document management and signature (Documalis), streaming training (TopFlix Academy), as well as projects in healthcare, logistics, finance and industry. Business complexity is preserved in full — indeed, that's your competitive edge. What Cybercoding standardises is everything that doesn't differentiate you in your market: technical architecture, security, regulatory compliance, identity management. Your specific business logic, on the other hand, is custom-coded.

ISO 27001 certification for a B2B SaaS follows a 4-step process: (1) Setting up an ISMS (Information Security Management System) — security policies, risk analysis, RBAC rights matrix, business continuity plan; (2) Technical documentation — PAS (Security Assurance Plan), PAQ (Quality Assurance Plan), BCP (Business Continuity Plan), DRP (Disaster Recovery Plan), technical architecture, immutable audit logs; (3) Internal audit — checking compliance before the external audit; (4) External audit by a COFRAC-accredited body — reviewing non-conformities and issuing the certificate. Using a traditional approach, this process takes 12 to 18 months and costs €100,000 to €150,000. With WakaStart, the delivered SaaS already natively embeds all ISO 27001 rules — documentation is generated automatically with every build. The subsequent COFRAC audit is fast and free of surprises. WakaStart does not issue the certificate itself (that is the role of the accredited auditor) but hands over the complete file so the audit is completed within a matter of weeks.

ISO 27001 and NIS2 are complementary but distinct. ISO 27001 is a voluntary international standard that certifies an organisation's Information Security Management System (ISMS). It is issued by an accredited body (COFRAC in France) and proves that the company manages its security in a structured, documented way. NIS2 (Network and Information Security 2) is a European directive, mandatory since 2024, which imposes legal obligations on all B2B digital service providers (SaaS vendors, hosting providers, cloud service providers): risk management, a business continuity plan, notification of significant security incidents within 24 hours, and supply chain security. In short: ISO 27001 is a certification you obtain voluntarily to reassure your clients — NIS2 is a legal obligation, non-compliance with which is subject to sanctions. In practice, an organisation compliant with ISO 27001 is generally NIS2-compliant too, but not necessarily the reverse. WakaStart natively embeds the requirements of both frameworks.

HDS (Health Data Hosting) is a mandatory French certification for any company that hosts, processes or stores personal health data. The list of organisations concerned is broad: telemedicine applications, digital patient records, SaaS for hospitals and clinics, e-health applications, medtech platforms, and medical coordination tools. Failure to comply is a criminal offence in France, punishable by fines and sanctions that can go as far as suspension of activity. HDS certification is issued by a COFRAC-accredited body and requires prior ISO 27001 certification. WakaStart relies on HDS-certified OVH infrastructure to guarantee the legal compliance of the health SaaS products it delivers. The WAKA-HDS module natively includes medical data partitioning (RLS by patient and by facility), automatic pseudonymisation, CNIL- and ANS-compliant audit logs, and the required HDS hosting contracts.

No — and it's important to be clear about this. WakaStart natively embeds ISO 27001 requirements into every SaaS it delivers: a documented ISMS, security policy, risk analysis, immutable audit logs, OWASP controls, an RBAC matrix, and automatically generated PAS/PAQ/BCP/DRP documentation. Official ISO 27001 certification is issued by an independent, COFRAC-accredited certification body — not by WakaStart. What WakaStart does is hand your COFRAC auditor a complete compliance file, with zero critical vulnerabilities, exhaustive documentation and an already-compliant architecture. The result: the audit is completed within a few weeks instead of 18 months, because the compliance work is already done. This distinction is not just a legal nuance — it ensures that your certification carries real value, issued by an independent third party.

GDPR (General Data Protection Regulation) imposes several precise technical obligations on any B2B SaaS processing the personal data of European residents: data minimisation (collecting only what is necessary), a documented legal basis for processing, an up-to-date register of processing activities, granular consent management (users can accept or refuse each type of processing), the right to erasure (users can request deletion of their data), the right to portability (users can retrieve their data in a structured format), notification of data breaches to the CNIL within 72 hours, and Privacy by Design (data protection built in from the design stage). Technically, this means: strict multi-tenant partitioning (one client's data is never accessible to another), encryption at rest and in transit, audit logs of access to personal data, and documented procedures for exercising data rights. WakaStart natively generates all these mechanisms in every SaaS it delivers.

eIDAS 2.0 (Electronic Identification, Authentication and Trust Services) is the European regulation updated in 2024 that governs electronic signatures and digital identity across the EU's 27 member states. It defines three levels of electronic signature: Simple (SES), Advanced (AES) and Qualified (QES). The qualified signature (QES) is the highest level — it carries the same legal value as a handwritten signature throughout the EU. The major novelty of eIDAS 2.0 is the introduction of the European Digital Identity Wallet (EUDI Wallet), available to all EU citizens. For a B2B SaaS, eIDAS 2.0 becomes relevant as soon as your application generates or collects contractual signatures (contracts, quotes, purchase orders, medical consents). Using non-eIDAS-compliant solutions risks your digital contracts having no legal value before a court. WakaStart's WAKA-SIGN module natively integrates eIDAS 2.0 qualified signature, compatible with the EUDI Wallet.

The NIS2 directive, fully applicable in France since 2024, imposes several concrete obligations on B2B SaaS vendors: (1) Documented risk management — identifying, assessing and treating cybersecurity risks using a formal methodology; (2) A business continuity plan — RTO (recovery time objective) and RPO (maximum data loss) defined and tested; (3) Incident notification — reporting any significant security incident to ANSSI within 24 hours; (4) Supply chain security — verifying the security of your technology suppliers and providers; (5) Encryption of data in transit and at rest; (6) Access management with strong authentication (MFA). Penalties for non-compliance can reach €10 million or 2% of worldwide turnover. Your large enterprise clients now systematically check your NIS2 compliance before signing. WakaStart natively integrates Zero Trust architecture and all NIS2 mechanisms.

With WakaStart, preparation for ISO 27001 certification takes 3 to 4 months for a new SaaS build, and 3 to 6 months for an overhaul. This timeline includes: bringing the SaaS into production (30 days for a startup), a bedding-in and monitoring period (30 days), documentation validation by your CISO or WakaStart's, and coordination with the COFRAC certification body. The ISO 27001 certificate is then issued by the external body after its audit. Without WakaStart, the same process takes an average of 12 to 18 months — because achieving technical compliance requires reworking existing code, often built without security constraints, and then producing all the documentation. WakaStart speeds up this process because the code is already compliant from the moment it's generated.

The WakaStart package starts at €30,000 excl. VAT for a startup (building a first SaaS, standard V1 profile), €55,000 excl. VAT for a scale-up (overhaul of an existing SaaS), and €90,000 excl. VAT for a large enterprise (modernising an application estate). These fees cover the entire development, deployment on OVH France, technical documentation, automated testing, and going live. Additional pricing options are: +€10,000 excl. VAT for ISO 27001 preparation, +€5,000 excl. VAT for HDS certification (health data), and €2,000 to €3,000 excl. VAT per WakaStart module activated (WAKA-SIGN, WAKA-DOC, WAKA-FACTURE, WAKA-SCRIBE). By comparison, the same project costs an average of €214,000 with traditional development (an IT services firm) and takes 12 to 18 months — 7 times more expensive and 12 times slower.

WakaStart's payment smoothing is a mechanism for financing the Build (the creation or overhaul of the SaaS) in monthly instalments — with no bank loan, no personal guarantee, and no impact on your balance sheet. In concrete terms: rather than paying €30,000 excl. VAT upfront, you pay around €2,000/month over 12 to 48 months. This smoothing is backed by the JDS Conseil holding company (WakaStart's parent company) — it isn't a bank loan but a payment plan offered directly by WakaStart. Monthly payments only start once your SaaS actually goes live — not before. No personal guarantee is required, there's no impact on your future borrowing capacity, and no bank surety is needed. This is particularly suited to startups wanting to preserve their cash flow during the phase of acquiring their first customers.

No — the WakaStart package is fixed and contractually guaranteed. This means that if WakaStart underestimated complexity during the Wakanalytics, that is WakaStart's problem, not yours. The budget does not increase after signature. What comes on top of the Build package are elements clearly identified from the Wakanalytics stage: the monthly Run service (OVH hosting, 24/7 supervision, updates), certification options (ISO 27001, HDS) if activated, the WAKA-SIGN, WAKA-DOC etc. modules if selected, and post-delivery feature developments (each development sprint is quoted separately). Unlike an IT services firm billing by the day rate, where the final budget can be 2 to 3 times the initial estimate, WakaStart commits to a fixed figure. This is one of the platform's fundamental contractual commitments.

Comparing the headline price is misleading — you need to compare the Total Cost of Ownership (TCO) over 3 to 5 years. An IT services firm bills development by the day rate (typically €500 to €800/day), with no commitment on outcome or timeline. For a startup-level B2B SaaS, the average budget is €214,000 (428 days × €500/day), with a 12- to 18-month timeline. That rate doesn't include: ISO 27001 compliance work (an extra €100,000 to €150,000), accumulated technical debt (to be fixed within 2 years), or maintenance and DevOps costs. WakaStart costs €30,000 excl. VAT for the same project, in 30 days. Over 5 years, factoring in maintenance, ISO certification and NIS2 compliance, WakaStart's TCO is 4 to 6 times lower than that of development through an IT services firm. The Wakanalytics produces a precise TCO comparison for your situation.

Yes. This is precisely the model designed for bootstrapped startups. For a €30,000 excl. VAT Startup Build package, smoothing over 24 months works out at around €1,250/month; over 36 months, around €833/month. The minimum monthly payment is €2,000/month (including Run — hosting, maintenance, supervision). This model is particularly suited to founders who want to preserve their cash for their first sales hires and marketing, rather than tying up €30,000 in development before earning their first euro of MRR. No bank loan is required to access this financing — which also makes it accessible to founders without an entrepreneurial credit history.

Migrating on-premise software to cloud SaaS is one of the most complex and riskiest projects in the software industry — because you have to transform the model while continuing to serve existing clients. WakaStart proceeds in 4 steps: (1) Wakanalytics — analysis of the existing codebase, identifying dependencies, mapping business rules, and drafting a modular migration plan; (2) Cognitive reverse-engineering — AI agents analyse the source code and interfaces to reconstruct the exact functional specifications, even without documentation; (3) Cybercoding rebuild — module-by-module regeneration on cloud-native architecture (Nest.js, Kubernetes, Keycloak IAM), while the on-premise version continues running; (4) Progressive migration — both versions coexist, with clients migrated one by one according to their own schedule. WakaStart offers 3 deployment modes simultaneously: shared cloud SaaS (new clients), dedicated cloud SaaS (large enterprises requiring physical isolation), and on-premise Runtime (clients unable to move to the cloud).

Yes — this is a contractual guarantee from WakaStart. The methodology is built around a Phase A of functional transposition: WakaStart rebuilds your SaaS identically on the new architecture, in parallel with the production version. Automated 1-to-1 tests validate that every feature behaves exactly as in the original version. The switch to the new version is carried out in production only once tests are 100% green — and a rollback plan is in place at every stage. Your clients keep using the old version throughout Phase A with no interruption. The final cutover is invisible to them. This isn't a promise — it's an architectural constraint: no go-live can take place without full validation of regression tests.

Cognitive reverse-engineering is WakaStart's method for analysing and understanding the behaviour of existing software — even without documentation, even with ageing code (Java 5, COBOL, VB6, PHP 4). AI agents analyse the source code, user interfaces, data flows and behaviour patterns to reconstruct the exact functional specifications of the software as it actually behaves — not as it was supposed to behave. This approach is fundamentally different from a requirements-gathering meeting: it starts from the real code, not from users' memories or outdated documentation. The result is a complete FSS (Functional and Security Specifications) document that your team validates before any generation takes place. This phase often uncovers business rules that no one explicitly remembered any more.

Yes. Cognitive reverse-engineering is specifically designed for old or poorly documented codebases. WakaStart has worked with Java EE, .NET Framework, VB6, PHP 4 and COBOL. The age of the language is not an obstacle — the AI agents analyse the application's behaviour, not the syntax of the language. In practice, the oldest codebases often have an unexpected advantage: their business rules are more stable and complete than in more recent code that is often still evolving. The main constraint isn't the age of the code but its testability: WakaStart needs to be able to verify that the new version behaves like the old one. For systems with no existing tests, WakaStart starts by building this reference test suite.

A full overhaul for a scale-up takes 3 to 4 months on average. This breaks down as: Wakanalytics (48h, free), Phase A functional transposition (6 to 8 weeks, depending on product complexity), Phase B feature developments and enhancements (2 to 4 weeks), and ISO 27001 preparation (in parallel or in month 4). For more complex projects — numerous business modules, multiple ERP integrations, large data volumes — the timeline can extend to 6 months. This timeline is calculated precisely during the Wakanalytics, based on the reality of your code, not on assumptions. The Wakanalytics is free and commits you to nothing — it simply gives you a precise figure.

100% in France, on OVH Cloud infrastructure. WakaStart uses two OVH datacentres in France (Roubaix and Gravelines) in active geo-redundancy — if one goes down, the other automatically takes over in under 4 hours. No data ever transits to servers outside the European Union. This architecture is particularly important for B2B clients who need to prove to their own clients (large enterprises, public sector) that their data is not subject to the US Cloud Act, which allows US authorities to access all data hosted by US companies, regardless of where it is physically hosted. OVH is a French hosting provider, not subject to the Cloud Act. For projects requiring total isolation (HDS health data, defence sector), WakaStart offers the on-premise Runtime mode: your SaaS runs on your own infrastructure, with no data ever leaving your premises.

WakaStart implements native Row-Level Security (RLS) at the PostgreSQL database level — the most robust isolation mechanism in the industry. In practice, every SQL query is automatically filtered by the tenant_id of the connected client. It is technically impossible for a query from Tenant A to access Tenant B's data — even in the event of a bug in the application code. Isolation is enforced at the database level, not just at the application level. This is a crucial point: many data breaches in multi-tenant SaaS stem from application bugs where a developer forgot a WHERE filter. With RLS, that bug can't cause a leak — the database refuses the query. This mechanism is verified with every build by SAST scans, and documented in the RBAC matrix provided to the ISO 27001 auditor.

Sovereign hosting means hosting on infrastructure owned and operated by a company that is not subject to extraterritorial legislation allowing access to data without the consent of its owners. In practice, US hosting providers (AWS, Microsoft Azure, Google Cloud) are subject to the Cloud Act (2018) and FISA (Foreign Intelligence Surveillance Act), which allow US authorities to demand access to data hosted anywhere in the world, with no notification or recourse for the companies concerned. OVH is a French company, with its datacentres in Europe, and is not subject to this US legislation. For B2B SaaS vendors handling sensitive data — HR, financial, medical, legal — sovereign hosting is not optional. It is a contractual requirement of most large French and European enterprises, and a condition for HDS certification.

WakaStart integrates post-quantum cryptographic (PQC) algorithms standardised by NIST in 2024: ML-DSA (Module-Lattice Digital Signature Algorithm) for cryptographic signing and ML-KEM (Module-Lattice Key Encapsulation Mechanism) for key exchange. These algorithms resist attacks from quantum computers, unlike RSA or standard elliptic curve cryptography. The concrete threat is the SNDL (Store Now, Decrypt Later) strategy: malicious actors are collecting encrypted data today in order to decrypt it later, once quantum computers become available. Sensitive data collected today must therefore be protected with quantum-resistant algorithms — starting now. WakaStart applies these algorithms to the signing of every build and every evidentiary archive. TLS 1.3 with Perfect Forward Secrecy ensures that a future key compromise cannot be used to decrypt past communications.

The on-premise Runtime mode is designed for organisations that cannot send their data to an external cloud — defence, critical healthcare, regulated banking, sensitive government bodies. It separates the design forge (which runs on WakaStart's secure SaaS Control Plane, on OVH France) from execution (which takes place entirely within the client's infrastructure). Process: (1) WakaStart generates and secures the application package on its SaaS Control Plane; (2) the package is cryptographically signed with ML-DSA (post-quantum signature); (3) the signed package is transferred to the client's infrastructure via hardened channels (DMZ, filtering gateway, or an encrypted air-gapped physical medium for the most sensitive cases); (4) on arrival, the signature is verified and a local SAST/DAST scan is performed to prove no modification occurred in transit; (5) the package is deployed onto the client's local clusters. No data, no secrets ever leave the client's infrastructure.

After go-live, the WakaStart Run team takes over the supervision and operational maintenance of your SaaS. This includes: round-the-clock monitoring with Grafana dashboards and real-time alerts, zero-downtime updates (hot deployments via CI/CD), incident management (on-call support, fixes, communication), automated backups twice a day encrypted with AES-256, SSL certificate renewal and security key rotation, and security updates (CVEs on dependencies). You don't handle bugs on a Sunday evening. You don't hire a DevOps engineer. You don't deal with security patches. All of this is included in the Run monthly fee. Your team can focus 100% on business value and customer acquisition.

Yes, fully and from day one. The source code generated by WakaStart is in TypeScript (Next.js for the front end, Nest.js for the back end) — two standard open-source frameworks maintainable by any development team in the world. Intellectual property is transferred contractually at go-live. You receive the complete source code via your private Git repository. There are no proprietary WakaStart components within the code itself — no SDK, no private library, no specific runtime. If you decide to stop using WakaStart tomorrow, you can take your code and have it maintained by any other team. This is contractually guaranteed and it's a non-negotiable WakaStart rule.

Yes. Every enhancement goes through the same Cybercoding cycle: specification → validation → atomic generation → SAST/DAST pipeline → deployment. Your code stays clean and free of technical debt with every update — which is the fundamental difference with traditional development through successive patches. The Run team included in your monthly fee handles zero-downtime deployments. You request a feature: it is specified, generated, tested and deployed in the following sprint. Unlike traditional development, where every change risks destabilising the existing system, Cybercoding ensures every enhancement is tested 1-to-1 against the existing architecture before deployment. Your users never see an update that breaks an existing feature.

The WakaStart Run service is the monthly operational service that keeps your SaaS running in production. It includes: hosting on OVH France infrastructure (Kubernetes, managed databases, S3 storage), round-the-clock supervision with automated alerts, corrective maintenance (fixing reported bugs), security updates (CVEs on dependencies, patches), automated backups twice a day, encrypted and geo-redundant, zero-downtime deployment of enhancements, technical support, and certificate management and key rotation. The Run fee is monthly and predictable — it's defined during the Wakanalytics based on the complexity of your SaaS and the level of service required. There's no surprise maintenance cost — unlike the IT services firm model, where every incident generates a billable intervention.

You receive the entirety of your source code in standard TypeScript/Nest.js, clean and documented, via your Git repository. Your application's Docker runtime is exportable — you can deploy it on any infrastructure without the WakaStart platform. There are no proprietary components in the code, no private WakaStart library to maintain. If you have a payment smoothing plan in progress, there are two options: settle the remaining Build balance (with no early repayment penalty), or continue with the agreed payment schedule. In either case, no exit clause holds you technologically hostage. This total reversibility is contractually guaranteed — it's a founding principle of WakaStart. We don't impose vendor lock-in, because we believe that if our work is good, you have no reason to leave.