• DeployBoard

Open Source

We have decided to rewrite DeployBoard and Open Source the code.

What does this mean? Users can run their own instance of DeployBoard in their own network, behind their own firewall, completely free of charge.

Why? My career was built on the success of Open Source projects, and this is my contribution back to the community.

Why rewrite? Why not just Open Source as-is? The current SaaS version of DeployBoard was built heavily relying on Amazon Web Services proprietary technology. Cognito for Auth, API Gateway/Lambda for the API, CloudFront/S3 for hosting the React Frontend, DynamoDB backend, SQS, SES and more. These services are great, but don't really fit the open source model. We want to maintain a direct port of the OSS project as a SaaS as closely as possible. It is not reasonable for us, with that goal, to be able to provide and maintain an OSS variant of those services and be able to offer the same quality as the SaaS product. For these reasons we have rewritten a lot of these services to work using other open source technologies that can simply run in a docker container, and be used in any customer environment.

What about the SaaS product? When the OSS project is complete (or at least in a compatible state) we will deploy a SaaS version of the OSS project and be migrating all existing users to the new platform. It looks a bit different than our current SaaS, but functions completely the same way from the end user perspective. I'd like to think we've made quite a few enhancements along the way as well, so I expect it to be a welcomed change.

How can I stay updated? You can follow along with development here:

23 views0 comments

Recent Posts

See All

How to measure the success of DevOps in your organization. There are four key metrics you want to measure when trying to determine how successful DevOps is in your organization. Deployment Frequency L