Payments, email, storage and workshop tools
Connect your PSPs with your own keys, your SMTP, external storage and Autotuner: infrastructure follows the way you work.
How it works
- 01
Connect payments
Stripe, PayPal, Mollie or Klarna with organization keys: you collect under your own merchant account.
- 02
Wire the infrastructure
Dedicated SMTP/Brevo, local storage, S3, Google Drive or Dropbox, plus naming templates for delivered files.
- 03
Set the workshop pace
Opening hours, SLA, vacation mode and Autotuner (.slave) decrypt depending on plan eligibility.
Stripe — your own workshop keys
Dedicated webhook, separate test/live modes: clients pay into your Stripe account.
Stripe — your own workshop keys
Dedicated webhook, separate test/live modes: clients pay into your Stripe account.
Why it helps
Multi-PSP without lock-in
Choose the provider(s) that fit your markets, with your own credentials.
Storage under your control
Local, S3, Google Drive or Dropbox: files stay in the infrastructure you selected.
Integrated workshop ops
Hours, SLA, vacation mode and Autotuner avoid bouncing between disconnected tools.
FAQ
- Which payment providers are supported?
- Stripe, PayPal, Mollie and Klarna can be configured at organization level, subject to your plan options.
- Where are ECU files stored?
- Depending on your configuration: platform local storage, Amazon S3, Google Drive or Dropbox, with naming templates defined in settings.
- What does the Autotuner integration do?
- On an eligible plan, .slave file decrypt can be automated through the Autotuner API configured for the organization.
- Can I export platform data?
- A data export is available at platform administration level (superadmin) for portability or global audit operations.
Ready to launch your white-label tuning platform?
Create your space, customize your brand and invite your first clients in a few minutes.