Crash Override

Chalk has a new home

1 minute read ||

Two weeks ago we quietly opened up chalkproject.io, and moved updated documentation for the Chalk project to the site.

We make heavy use of Chalk in the Crash Override platform, but we are far more than a hosted version of Chalk, and we didn't want to confuse our users. Chalk is an enabling technology that allows us to connect code with services, and collect deep telemetry as it runs through CI/CD along the way, but we use that data and more and then perform magic to connect it all together to create the Crash Override data catalog. We then keep that always-up-to-date to act as a change ledger and allow users to not only see changes that have occurred, but to deeply inspect the change such as look right inside of build internals. 

In the coming weeks the Chalk engineers will be going over some of the updates that have happened since we last posted about it, shamefully a long time ago, and sharing new features that are being released soon including a version of Chalk for serverless functions. 

Yes you heard that right, the ability to trace code from a code repo to a serverless function.

In the meantime here are the new links

Docs (recently updated) - https://chalkproject.io/docs/

Binaries - https://chalkproject.io/download/

Source Code - https://github.com/crashappsec/chalk

We will be opening a community Slack workspace soon and there will be a Chalk channel for discussion and support but if you need help now, just open a ticket and we will be there.

Subscribe for our latest news

Promise that we won’t spam and that we’ll send only one email a month.

Is Crash Override for you?

Honestly? We don’t know until we sit down to talk. 
But we’re not going to bend your ear or twist your arm to sell you a solution you don’t need. 

Instead, we’ll take 30 minutes to demonstrate what Crash Override can do and how it solves DevOps difficulties.

Take a VIP Tour