A developer from your team takes a feature in hand.
The platform keeps the checks and the go-live. Your developer codes on their own machine. The platform reviews, tests and delivers their work like the rest.
What your team gains
- 01
The platform takes care of the heart of the application: its data model, its access rights and its security. It keeps them consistent as the application evolves. Your team concentrates on the features specific to your business.
- 02
Nothing changes in its habits: your team keeps its usual development environment — workstation, code editor, coding assistant and Git.
- 03
Your team can keep control of the specific work: integrations, complex calculations, bespoke interfaces.
How it works
- 1
Ask: the project owner asks for the feature and invites the developer, with the Developer role.
- 2
Download: the developer downloads the kit, the project's code and the tools to work on it, onto their own machine.
- 3
Code: the developer writes the feature with their usual tools, coding assistant included.
- 4
Push: the developer sends the work on the feature's branch.
- 5
Hand back: the platform reviews, tests and delivers the work, like the rest.
What the developer can do, and what stays with the platform
- 01
The data model is described to the platform, in a few words. It checks it and applies it.
- 02
The developer sends their work only on the branch of the feature.
- 03
No key and no password in the code: any push that contains one is refused.
- 04
Security stays with the platform: access rights, data isolation and penetration tests also cover the developer's code.