Note

Attini is still in beta and the prices are only indicative so they might be subject to change with short notice.

Pricing

Attini is prices based on the number of steps in your Attini deployment plans per environment per month.

This means that you only pay for the first (or longest) execution per month, then you can re-run your deployments for free.

Pricing table

Steps*

Price

Payment model

0-10

$0

N/A

11-36

$25

Fixed monthly

37-87

$0,5

Per step

88-188

$0,25

Per step

189-429

$0,1

Per step

430+

$0

N/A

* A Step is counted as one state in the underlying AWS StepFunction. So one execution with a 100 steps will cost more than an execution with 15 steps.


Detailed information

  • We use a progressive pricing model meaning the more steps you have the less you pay for each tier. For example if you have 38 steps you will pay $26 ($25 for the first 36 steps and then $1 for the remaining 2 steps).


  • You only pay for active deployment plans, so if no deployments are run, Attini will be free.


  • The price is counted for the longest execution per month. Which means if you remove a stop from a deployment plan and redeploy the distribution, the shorter plan will not have effect on the pricing effect until the following month.


  • We will summarize all steps for all deployment plans in one environment. An environment is counted based on its Name, AWS Account and AWS Region. So if you for example run 2 environments with the name development in 2 different 2 different AWS regions. You will be invoiced for 2 environments.


  • An Attini deployment plan always starts with an “get deployment data step”. This step counts against your bill. This means that the minimum amount of steps a deployment plan can have is 2 (the “get deployment data step” and your own step).


  • Orchestration steps like Map and Parallel will result in 1 additional step because the tasks within the Map or Parallel step will be counted individually, then the Map or Parallel step itself will be counted.


  • If one or more tasks within a Map or Parallel fails, only the successful tasks will count. Meaning that the Map or Parallel step will not count, only the successful tasks within it will.


  • If you rename a distribution, that those steps in the deployment plan will count twice for one month. This is because we use the distribution name to identify if a deployment is a re-run (free). So with a new name, it will count as a first run of the month deployment. To avoid this you can change the name on the first deployment of the month. If you raise a support ticket with us, we can credit the double cost as long you don’t do this repeatedly.


    The same thing happens if you “move” steps from one deployment plan to another during one month because we count the longest execution. Example if you have 30 steps in your network deployment plan, and 40 steps in your platform deployment plan and move 10 steps from network to platform (assuming you have already deployed both distributions this month). The longest execution for network will be counted as 30 steps, and the longest execution for platform is now 50 steps which gives a total of 80 steps. Next month the invoice will only be for 70 steps because you only have 20 step in your network deployment plan and 50 steps in your platform deployment plan.


Examples

Midsize installation

A customer have the following setup:

  • One distribution called “network” with 10 steps

  • One distribution called “platform” with 20 steps

The network distribution sets up a VPCs, subnets, security groups etc.

The platform sets up databases, EKS, Cloudfront etc.

The company use network and platform in 3 environments:

  • development

  • staging

  • production

So network and platform have total of 30 steps per environment which cost $25*3=$75

Total: $75

Large installation

A customer have the following setup:

  • One distribution called “network” with 15 deployment plan steps

  • One distribution called “platform” with 40 deployment plan steps

  • One distribution called “devtools” with 30 deployment plan steps

  • One distribution called “central-network” with 8 deployment plan steps

  • One distribution called “backoffice-applications” with 15 deployment plan steps

The network distribution sets up a VPCs, subnets, security groups etc.

The platform sets up databases, EKS, Cloudfront etc.

The devtools sets build servers, log servers etc.

The central-network sets up a VPC with a AWS Transit Gateway and associated resources.

The backoffice-applications sets up a Active directory, exchange servers, VPN etc.


The company use network and platform in 5 environments:

  • development in eu-west-1

  • staging in eu-west-1 and us-east-1

  • production in eu-west-1 and us-east-1

They have 1 environment each for devtools, central-network and backoffice-applications

So network and platform have 55 steps (15+40) per environment which cost ($25+$9.5)*5=$172.5.

So devtools have 30 steps which cost $25*1=$25.
So central-network have 8 steps which cost $0*1=$0.
So backoffice-applications have 8 steps which cost $25*1=$25.

Total: $222.5

Billing data collection

For billing purposes Attini will collect some usage data. This data will only be used internally at Attini and it will not distributed to anyone. The data is collected during the deploys, so if you do not use the Attini framework, no data will be sent to us.

What data do we collect:

  1. AWS Account Id

  2. AWS Organization Id

  3. AWS Region

  4. Environment name

  5. Distribution name

  6. Attini framework version

  7. Execution arn of your deployment plans

  8. Number of steps in your deployment plan executions

  9. The email provided in the attini-setup CloudFormation stack if it has been configured

Note

If you tamper with the data collection to avoid invoicing, we will disable your ability to do new deployments.

We will try do send an waring email before we disable the framework if you have configured an email in the attini-setup CloudFormation stack.

We can enable the Attini framework at any time.