Kleeen and Your Organization

A common question we get as people evaluate Kleeen's platform is how does this fit into my organization. The easy answer is that Kleeen is a platform built by developers to make better software a better way. As developers, we built the tool that we would want to, and do, use to build software and follow best practices. If you use the Kleeen platform, you are using tools built with our tools. 

For your organizations here are some important points about how Kleeen functions in a development organization:

• Just like any other developer, Kleeen will check updated code into your Github Repo using a Pull Request and only change the code sections that need to be updated.
• Kleeen's code is well-formed, commented and human-readable.
  • In this example, a widget has been specified and the place to insert an endpoint marked with "TODO:".
    import { DispatchCustomActionResults, CustomActionArgs, AuthContext } from '../../../types';

    
    

    //  Widget: Reboot Sensor

    // Chart type: [WIDGET] CUSTOM_ACTION

    export const custom_action_3b73adbb_d755_414b_b017_1d964567aa2d = async (

      input: CustomActionArgs,

      context: AuthContext,

    ): Promise<DispatchCustomActionResults | 'not implemented'> => {

      // TODO: add your code here.

      // If you need to access the current user, the token and data sources,

      // you can get them from 'context'

      return 'not implemented';

    };
• Kleeen code is built on common components and not proprietary. 
• Kleeen doesn't hold your code hostage in a mystery box, once exported it is your code to own, manage, and love.
• Kleeen builds a foundation, not a fence. We knew from the start that making a tool that does everything for everyone is impossible. Instead of failing at this, we give you the opportunity to reserve custom areas for your secret sauce.
• Future proof your application: rbac, style, and security are all baked into Kleeen's output and are just three of the ways we help fight unnecessary technical debt.
• Continue using your existing code review process.
• Build an application that leverages your existing data lakes, database, and api's.