Inside a public organisation the question is rarely just whether something works. You also have to show which officers may open a resident's file, when a backup was last restored in earnest, and what the accessibility statement on your website actually claims. We run your systems entirely at a distance and write those pieces along the way, not on the eve of an inspection.
A village council of four thousand residents, an inter-municipal body and a secondary school share neither budget nor legal duties, but their weak points rhyme: an ageing file server, accounts belonging to staff who left years ago, and a public website nobody has ever measured.
A risk analysis drafted together with your departments, hardened access, alert monitoring and a written route for reporting an incident, following ANSSI guidance and CERT-FR bulletins. We prepare the ground for NIS2 as transposed into French law, without pretending to decide on your behalf how your organisation is classified.
A record of processing kept current, signed agreements with the publishers of the software your departments actually use, permissions granted by role rather than by habit, and logs the DPO may open at any hour. We also assemble the technical input for an impact assessment. More in GDPR and personal data protection.
Your website and online forms measured against RGAA 4.1 and WCAG 2.1 AA, the most obstructive failures corrected first, then the accessibility statement and the multi-year plan written up. See Public sector websites.
Entra ID, Intune, Microsoft 365, file servers and backups, whether in a town hall, across a group of schools or in an organisation spread over several buildings. Whenever the hardware itself has to be touched, to change a disk or re-patch a rack, your own officer or your local contractor carries it out while our engineer guides them on a video call.
Technical connection of your online services to FranceConnect, an electronic signing folder and qualified signatures under eIDAS for council decisions and contracts, plus transfer plans towards electronic archiving. The aim is plain: one absent colleague should never hold up a signature again.
Extracting and publishing the open datasets expected of your organisation, in formats people can actually reuse rather than scanned pages, refreshed automatically wherever the source allows it. Online forms can also be wired into your internal tools so nobody retypes the same details at the counter.
The procedure, its form, its publication and its deadlines belong to the buyer, who applies the French procurement code. Apply stands on the supplier side: we set out what is feasible from a distance, we price it, and we answer when you consult the market. Advising you on your own procedure is not our role.
Ahead of any publication you may ask us to help size the requirement. Back comes an order of magnitude and a list of the services involved, ready to drop into your budget planning.
A remote audit produces the numbers usually missing from a specification: workstations and servers, licences genuinely in use, versions past end of support, and the weaknesses that deserve priority.
Publish on your buyer profile, on the PLACE platform or through your purchasing group. We submit in the form requested, European Single Procurement Document included, and answer clarification questions inside the stated deadlines.
Implementation and ongoing operation as the contract requires, a signed record at each phase, reporting at the agreed frequency, and invoices filed on Chorus Pro quoting your commitment number.
For a live consultation, write to tender@apply.fr, the mailbox kept for public procurement. Attach the specification even in draft, and you will get a frank answer about which lots we can carry out remotely and which ones fall outside what we do.
A public contract lasts a limited number of years. Everything we produce is therefore written for two readers: the officer who will operate the system tomorrow, and the supplier who takes over the lot after us without going back to a blank page.
The starting point for any programme of work. Findings ranked by urgency, each with an order of magnitude alongside it.
Worth reading before buying a single tool. It separates what the rules and your own duties truly demand from what a salesperson would like you to sign for.
Written for your organisation, not lifted from a template. Security policy, the rules that govern permissions, continuity and recovery planning, with more in Security policies and documentation.
Backed by a real test, page by page. State of conformity, the gaps found, reasoned exemptions and a contact route for users, refreshed after every redesign.
Delivered at whatever rhythm the contract sets. Requests handled, deadlines met, changes applied and restores tested, in a layout that feeds straight into contract supervision.
Handover is planned from day one. The inventory, the diagrams, the credentials deposited in your own password vault and the operating instructions all belong to you. Once the term expires, whoever follows picks the work up from written material rather than from the goodwill of the departing supplier.
The buyer, and nobody else. Choosing the route, drafting the pieces, assessing bids and awarding the contract rest with you and your advisers under the French procurement code. Our part is that of a candidate: technical data drawn from an audit, a description of the services we run remotely, and a price.
Yes, as soon as the public body asks for it. The invoice carries the contract reference, the executing department and the commitment number exactly as you supply them. Ongoing operations are billed monthly, project phases once each acceptance record has been signed.
Through encrypted remote access. Accounts are named, sessions are recorded and your departments may review those recordings whenever they wish. No visit appears anywhere in the contract. For anything physical, our engineer walks your officer, or the firm that services the site, through the sequence on a video call and then verifies the outcome remotely.
Yes, as soon as the work touches personal data for which you are the controller. If your DPO already keeps a template, we start from it, attach the list of sub-processors and spell out the technical measures in place.
No, and nobody honest will. Compliance also depends on your software publishers, on internal working habits and on decisions that are yours to take. What we do commit to is the work itself: measuring what exists, fixing what falls inside our remit, documenting the remaining gaps and telling you plainly where you stand.
Describe the requirement or attach your draft specification. You will get a proposed scope and an indicative price, usable for budget planning or for sizing the contract.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.
