Terms of Service

Last updated

What you are getting

Flowblocks is workflow infrastructure: a builder you embed in your own product, the APIs and SDK around it, and a service that runs the workflows built with it. Using any of it means agreeing to these terms. If you use it for a company, you are agreeing for that company and confirming you are allowed to.

Your account

You are responsible for what happens under your account and for keeping the way into it safe, including your API keys. Tell us promptly if you think somebody else has got in. One person per account; a team shares workflows, not a login.

Plans and payment

  • Developer is free. It is for building and testing, with your own model keys.
  • Cloud is charged by the workflow run, at the rate shown on the pricing page when the run happens, and billed monthly in US dollars, plus any tax your jurisdiction adds. Starting credits are spent before anything is charged and cannot be exchanged for money.
  • Enterprise is covered by the agreement you sign with us. Where that agreement and these terms disagree, it wins.

A run counts once it starts, whether it finishes, fails or is stopped part way. If we change the rate, we will say so here and on the pricing page at least 30 days before it applies. Payment is taken by Stripe; we never see or hold your card details.

Refunds

Usage that has already run cannot be handed back, so charges are not refundable in the usual sense. If we charged you for runs that failed because of a fault on our side, write to us within 30 days and we will credit them.

What is yours

Your workflows, the data that moves through them and the results they produce are yours. You give us permission to store and process them for one purpose: running the service for you. We do not use them to train models, and we do not look at them except to fix a problem you have asked us about or to keep the service secure.

The builder, the SDK and the service stay ours. You may embed the components in your own products for as long as you have an account; you may not resell Flowblocks itself, or offer it to others as a workflow platform of your own.

The people who use your product

When you embed Flowblocks, your users build and run workflows through you. You are responsible for them: for what you let them do, for having the right to send us their data, and for telling them how it is handled. Their runs are your runs, and are billed to you.

Connections and models

Workflows act through accounts and tools that somebody connected: mailboxes, calendars, file stores, MCP servers. A workflow does what it was built to do with the access it was given, so connect only what you are entitled to and grant only what the workflow needs. Those services have their own terms, and those terms are between you and them.

Steps that call a model produce output we cannot predict or check. Review what matters before acting on it, and put an approval step in front of anything that cannot be undone.

What you may not do

  • Break the law, or help somebody else to.
  • Send spam, or run workflows that harass, defraud or deceive people.
  • Reach into accounts, systems or data you have no right to.
  • Probe, overload or work around the service’s limits, or resell access to them.
  • Use the service to build a competing one.

The line is straightforward: automate your own work and your users’ work, with their say-so. If you are unsure which side of that a plan falls on, ask before you build it.

Availability and support

We work to keep the service running and will tell you about planned interruptions when we can. An uptime commitment exists only where an Enterprise agreement states one. Support is through the channels listed for your plan on the pricing page, and covers Flowblocks as shipped rather than your application or the services you connect to it.

Ending it

You can stop at any time by deleting your account; you owe only what has already run. We may suspend or close an account for a serious breach of these terms, or for unpaid charges. Where the problem can be fixed, we will ask first. After an account closes you have 30 days to export your workflows and run history before they are deleted.

No warranty

The service is provided as it is. We do not warrant that it is free of defects, that it fits any particular purpose, that a model’s output is correct, or that a service you connect will keep working the way it does today.

To the extent the law allows, our total liability for anything arising out of these terms is limited to what you paid us in the twelve months before the claim. We are not liable for lost profit, lost data, or any indirect or consequential loss.

Changes

We may update these terms. Material changes will be noted by the date at the top of this page, and if you have an account we will email you before they take effect. Carrying on after that means you accept them.

Contact

Questions about any of this go to support@flowblocks.dev.

Start building today

Create an account in minutes, or talk to our team about an enterprise plan.

Kobra Systems

Collection of 120+ polished motion components for building delightful interfaces in React.

Browse components

Krafa

Curate your design taste from X, Pinterest and more. Your agents learn it and build every screen to match.

Try Krafa