Your Business Central AL extensions, built by a supervised team of agents.
Delivery, functional and product departments work in parallel, each with its own agents, its own rules and its own approvals. You keep the design, the review and the signature. The platform does the typing, and proves what it did.
- src
- SalesHeaderExt.al
- ApprovalLevel.Enum.al
- ApprovalSetup.Table.al
- app.json
// Unit 4 · developed by an agent, reviewed, compiled tableextension 50104 "Sales Ext" extends "Sales Header" { fields { field(50100; "Approval Level"; Integer) { Caption = 'Approval Level'; DataClassification = CustomerContent; } } }
More customisations, with the same team.
Independent units of work are developed at the same time, not one after the other. Your consultants and developers spend their time on design and review.
Your development rules, naming and patterns are written once as rule cards and templates. Every agent, on every project, follows them.
Requirements and guidelines are anonymised with your own dictionary before any AI model reads them. The model works on placeholders, never on your customer's names and figures.
Three departments, working in parallel.
Each department is a district of your platform, with its own people, agents, rules and gates.
Customer projects, from the approved requirements to the compiled .app. Several developer agents build units of work at once; reviewer agents check each one before it reaches a person.
Analysis and specification. Agents turn documents, emails and meeting notes into structured requirements and a plan of work that your consultants validate.
Your own vertical or AppSource extension: each roadmap item becomes units of work built to the same standard, release after release, with the whole history in the register.
Parallel, multi-agent, and always supervised.
Nothing leaves the sandbox until the gateway allows it and the right people have signed.
- 1 Analyst Reads the anonymised requirements and asks what is missing.
- 2 Planner Splits the work into units and their dependencies. You approve the plan.
- 3 Developers Independent units are built in parallel, each with the rule cards it needs.
- 4 Reviewers Check each unit against your development rules; failures go back for rework.
- 5 Compiler A real AL compile, repeated until it passes. The .app you get is the one that compiled.
- 6 Release gate Pull request and publish go through the gateway. Production needs two different people.
Engineered to be trusted with customer code.
A multi-agent system is only as good as the walls around it. These are ours.
Runs the agents and their sequence: analysis, plan, development, fix, rework, translation. Domain knowledge lives in packs, not in code.
The AL compiler runs against the symbols of your target version. Code that does not compile never reaches a reviewer, let alone a customer.
Every action that leaves the sandbox — branch, push, pull request, merge, pipeline, publish — is proposed to the gateway, which applies rules, levels and approvals. Agents never hold a credential.
Unlimited users and roles. Permissions follow the role, sensitive actions ask for a fresh sign-in and a second factor, and a release to production needs two different signatures.
A dedicated environment in the Azure region you choose: resources of its own, managed identities, no password in a connection string, ready within 120 minutes.
Azure DevOps and GitHub: branches, pull requests and pipelines live in your own repositories, under your policies. Each repository says where it is, and a run goes where its repository is.
Business Central packs with agent prompts and rule cards. Reviewer agents check naming, structure and the development rules you set, and your own guidelines become cards the agents follow.
Requirements and guidelines are anonymised with your own dictionary before any model reads them. The engine accepts only anonymised text: it is a type, not a habit.
Every decision is written to an append-only chain, each entry sealed to the one before. Change a row and the verification fails.
Under the hood: a dedicated platform on Azure.
Every customer runs the same reference architecture in an environment of their own, in the Azure region they choose. These are its parts.
- Your people's accountsSign-in with an authenticator; users and roles are managed by you, in your workspace's settings
- SiteChat, plans, approvals
- OrchestratorAgents and packs
- CompilerAL compile service
- GatewayRules, approvals, audit
- Azure SQL DatabaseRuns, approvals, people
- Azure Key VaultCredentials, never in code
- Azure Blob StorageImmutable audit chain; .app files held for download links
- Azure DevOpsBranches, pull requests, pipelines
- GitHubBranches, pull requests, issues
- Claude APIYour API key, your costs
What you need to start
Business Central, a repository in Azure DevOps or GitHub where the agents' branches and pull requests land, and an API key for the AI model. Your environment is ready within 120 minutes of the payment.