When an application outlasts the team or supplier that built it, who can still change it? For a director, the answer affects the next contract negotiation. For an IT manager, it affects whether a second team can take on the work this year. For a developer, it comes down to something practical: can I get the source, understand the rules that apply, and run it on my own computer?
Where governance becomes expensive
Many larger organisations already control what reaches production. The cost can arise much earlier. A developer needs access to one application. The repository owner works from one list of teams and the environment administrator from another. A reviewer needs to establish which guidelines applied when work began. By the time the release owner sees the change, several people have reconstructed facts that were already known when the work was assigned. The approvals may all be justified. Repeatedly gathering the same evidence consumes time that is hard to see in a project estimate.
For a smaller organisation, the same issue looks different. Imagine a distributor whose software partner maintains its dispatch application. The owner wants to bring in a second partner for one change. Where is the current source? Can the new developer test a change with sample data? Can the owner give them access to dispatch without also giving them access to payroll? A small team needs credible answers to those questions even when it has no dedicated platform department.
What low-code solves, and what to examine
Low-code and no-code products address a real need here. A shared development model, familiar components and a standard path through testing and release can simplify governance and delivery. The buyer still has to examine what is specific to the vendor. Can two developers work independently on branches and review the result using the team's own tools? What would it take to run the application elsewhere? How does the licence bill change as more people use it? The answers vary by product and contract. They matter most once an application succeeds and replacing it becomes expensive.
AI-assisted development changes who can produce or modify source and which tools they can use. It leaves the organisation with familiar decisions about ownership, access, testing and continuity. Even good generated code cannot tell a new colleague which repository the company considers authoritative or who is allowed to publish from it.
Why Two Swallows built FlightDeck
Two Swallows is the IT department for SMEs and healthcare organisations, or brings specialist engineering and architectural experience to an existing IT department. Erwin Schmidt brings the perspective of someone who built and sold an IT company. Jurgen Bettonviel focuses on whether the proposed technology can be operated and maintained. Their starting question is what the client needs IT to deliver. FlightDeck gives that way of working a practical form when teams use AI to develop software.
FlightDeck applies that approach to each application. The client keeps editable C#/.NET source in a GitHub or Gitea repository under its own control and chooses the servers that host the shared environments. In Management, an administrator records the application, its repository, its environments and the revision of the guidelines. The administrator grants a developer access to that application in a particular environment. The developer opens a personal branch in VS Code, with the corresponding guidelines and their choice of approved AI assistance. A colleague can inspect the same source, run it and make a different change on another branch.
Business work fits within the same model. A BI team, for example, can design a dashboard in the Business environment under the organisation's guidelines. Reading data from another environment requires separate, approved read-only access. Permission to develop the dashboard does not confer permission to query production.
What you can verify yourself
Larger organisation. Take one application that two teams already maintain. Give each developer access to the same application in Development. Have them open their personal branches and compare the guideline revisions. Then remove one assignment and repeat the checkout. This shows which decisions the platform enforces and where the organisation must still act. Revocation blocks future checkouts; a copy already on the developer's machine stays there.
SME. Pick an application another supplier might need to maintain. Ask a second developer to open its repository, run it using local test data and explain how to make a small change. Check who controls the Git account, the hosting and the backups. That exercise gives the owner evidence of portability. Moving a live service also requires its data, configuration and operating instructions.
Start with one application
Bring one application, its business owner and someone who maintains it to a conversation with Two Swallows. Choose a change that crosses a real handover. Trace where time is spent obtaining access, finding the right source, testing and assembling evidence. Then agree what a pilot should demonstrate, who will run it and what it will cost. For an SME owner, the test might be handing the application to a second maintainer. For a larger organisation, it might be onboarding a second development team under the same rules while retaining control of source and hosting.
Updated on