The anti-lock-in pledge
Lock-in is not a business model.
Six clauses, in writing — because “you can leave anytime” only counts when it’s true. These are implementation commitments, not claims that every future capability already exists.
Export before exit.
Before paid launch, we will publish and test the data export that each live product surface supports — not pretend an unbuilt export exists.
Exit terms before launch.
Before paid launch, we will publish the cancellation, export, and support terms that apply to each offered service.
Billing is never a hostage.
We will document the provider-supported billing transition before launch. We do not claim a card or subscription port that the provider cannot perform.
Operational commitments before launch.
Before paid launch, we will publish the uptime, support, and provider terms that are actually in force.
Scope before commitment.
Custom domains, white-labeling, and other future features are not promised until they are implemented and documented.
Deletion terms in writing.
Before paid launch, we will publish the deletion process, retention periods, and any legal exceptions that apply.
Each commitment becomes public product behavior only after it is implemented and tested. Current commercial terms are confirmed with each design partner before access is granted; read the status at /fees .
— the founders, community.io