Skip to content
KostrixBeta, home

Contact Kostrix: ask before you sign up, if you would rather.

You do not need to talk to anyone to start: create an account and run a scan. This page is for the questions that come before that - a security review, an estate of several accounts, or what one of the 235 checks actually measures.

Tell us what your security team or your finance team will ask.

What is this about

Opens your mail client with the message filled in. Nothing reaches us until you press send there.

Directsupport and sales

support@kostrix.com

Plan requests and questions go here; the form composes a message to this address with what you filled in, so nothing is sent until you press send in your own mail. Something not working? Use the support page or write to support@kostrix.com: that opens a ticket with a reference.

Security reviews

The whole access footprint is one CloudFormation stack, and the policies it creates are published in full on the security page. Send that to your reviewer before you send us anything, and most of the conversation is already over.

Several AWS accounts

A Kostrix account is bound to one AWS account - the one AWS reports when you link it - so an estate is several of them. If you are scanning many accounts and need findings to stay attributed per account rather than merged, say so here and we will work out the arrangement.

Before you write

If the question is whether Kostrix can stop an instance, delete a snapshot or resize a volume for you, the answer is no, permanently. It recommends and you act.

The four questions that come up first

What does it actually check?
235 named rules across storage, compute, networking, databases, serverless, containers, ML and governance, plus Savings Plans and reserved instance coverage. All of them are listed on the features page, with the identifier each one stamps on its findings.
Can it change anything?
No. There is no mutating AWS call anywhere in the product, and the policy you deploy grants read actions only - Describe, List and Get, plus a few scoped reads under other verbs that the security page names one by one - so there is no write permission in it to use. CloudTrail on your side records what it does.
Where do the savings figures come from?
Counts and sizes from the account, rates from the AWS Price List API, and every term printed beside the result so you can multiply it out yourself.
What does a first scan not cover?
Whatever the reconciliation says it did not cover. On our own account that was 18 of 34 billed line items, and that list is shown in the product next to the savings rather than being left for you to infer.