About Synesty Studio:
Synesty Studio is a cloud-software you are renting monthly - so calledSoftware-as-a-Service. The cost depend are usage based. Depending on your specific requirements you need a combination of Base-packs, Add-Ons, Runs, Traffic and Records.
Let's say you want to update the stock of 5000 products of your shop system every 4 hours. The data will be provided in a CSV file via FTP. You also want to recognize when there are new products in the CSV file. For that you need to store the records in a datastore.
That means you need 5000 rows of datastore storage, file transfer from FTP and functionality from the shop Add-On. All of this can be accomplished in 1 flow. Running this flow every 4h results in 186 flows per month.
Divide your requirements into single executable and automizable processes - that is what we call Flows. For example, write down all your interacting systems on a sheet of paper and draw an arrow each for every process (e.g. transfer data from A to B). Each arrow could represent a flow.
Think about how often you want to run a flow. Multiply this with the number of days in the month to estimate the required number of runs per month. Remember that you can also skip hours or days to save runs. Alternativly you can trigger flows manually or via URL from an external application.
Data Traffic is hard to estimate. Each file or API is different. Just use the trial period to runs flows and get a feeling the amount of traffic needed. The flow event-log shows the used traffic after each run.
It depends on your specific use case if you need to store data or not. Example: In some use cases when importing data you need to find out whether a record is new records or already exists. In this case it is needed to store data in datastores, so that you can make this distinction.
Each time you use a Step which creates a usable output (e.g. a file, FTP-Upload or a webservice call) this step is considered an Export-Step. In average flows have 2 Export-Steps, but you need to try, as it depends on your requirements.
Yes. You can configure the scheduling so that you can skip specific hours and days.
This can save runs and reduce monthly cost.
Starting at the Starter-pack it is also possible to trigger Flows via URL from external applications. This gives you even more control about when and how often flows are executed.
Contract term 1 Month:
The regular billing period is one full month. Normally you will receive the invoice at the last day of the month.
If you purchase an add-on not on the first day of the month, then the billing period is 30 days.
The billing period will be automatically adjusted to the full month (from 1. to the last day) within the next month.
This adjustment process simplifies the whole billing process with the goal that we can send you a single invoice per month instead of many small invoices.
Contract term more than 1 Month: For contract terms longer than 1 month the following rules apply: You will receive the invoice at the same day of the purchase for the complette billing-period (pre-paid). (e.g. for a contract term of 12 month your invoice will contain the full amount for one year.)
The invoice amount is due 14 days after invoice date and will be fetched with the configured payment method.