MAINSYSTEMS 
Developers · Lifecycle
From change to operation with a known path.
Work in separate versions, use checkout and selective merging, publish to dedicated addresses and investigate applications with Radar.
APPLICATION LIFECYCLE
Work, publish and observe without losing context.
KEPLIN separates the version under construction from the version served to users and preserves a readable trail of change.Create a safe line of work.
Each person can choose their version, create new versions and work without changing what is published.
Selective checkout and merge.
Lock an element while editing it and carry only chosen changes between versions.
Associate an address with a version.
Each host explicitly meets the defined version, with its own application login, users and permissions.
Revert a change or reset a state.
History allows you to go back with granularity and understand who made each change.
OBSERVE
Radar by application and overview.
Analyze calls, times, sessions and errors; Follow the timeline of an issue and set up alerts.
Continuous delivery with memory.
The platform maintains the relationship between what was built, what was published, and what happens in use.
VersionsIsolated work
CheckoutSecure collaboration
HistoryRollback and reset
RadarObservable operation