Customisations - coming soon

Custom vehicle tuning database control for advanced Remapdb teams

Customisations is a planned Remapdb feature designed to give advanced businesses deeper control over vehicle tuning data, ECU file-spec notes, custom records, imports, and customer-facing output across widget and API experiences.

Planned feature. Not available yet. Built for advanced vehicle tuning database control.

Coming soon

Planned, not live yet

Customisations is currently in roadmap planning and not available inside the product today.

Available now

Use today's Remapdb products

Widget, dealer locator map, WordPress plugin, API options, quoting, branding, pricing controls, and support are live today.

Best next step

Register your interest

Tell us which data-control workflows matter most so roadmap priorities reflect real demand.

Planned capabilities

What Customisations unlocks

Customisations is planned for teams that need deeper control over records, values, and output logic while keeping one operational data layer inside Remapdb.

Edit vehicle records

Modify vehicle, model, engine, ECU, stage, and customer-facing tuning-data fields where supported.

Control tuning parameters

Adjust stock and tuned power, torque, kW, gains, stage values, ECU file-spec notes, and display logic.

Upload your own database

Import structured vehicle tuning database records and manage them from one control layer.

Create custom records

Add vehicles, engines, variants, services, notes, and business-specific internal data.

Override shared data

Use Remapdb maintained data as a base, then apply your own corrections and custom logic.

Power widget, API, and AI-assisted workflows

Use customised records in tuning widget flows, remap database API workflows, quote forms, AI integrations where supported, and future modules.

Why it matters

Shared data launches. Custom data differentiates.

Advanced teams often need their own tested tuning values, compatibility notes, and business-specific data standards reflected in customer-facing journeys.

Advanced tuning businesses

Control the data your customers see and keep output aligned with your standards.

Dealer networks

Manage services, pricing, and dealer-specific data behavior with deeper precision.

Online file providers

Connect your own file-service catalogue, ECU file specs, and records to the customer journey.

Cloud platforms

Use custom vehicle tuning database data in dashboards, portals, API workflows, and internal operations.

Product and parts websites

Manage compatibility and performance records tied to product-led journeys.

How it may work

From imported data to customer-facing output

Final implementation may evolve, but the intended workflow stays straightforward and operational.

1

Start from the Remapdb database

Use the maintained vehicle tuning database as your foundation.

2

Edit or override records

Adjust vehicles, engines, stages, values, notes, and key fields.

3

Upload your own data

Import structured data from your own catalogue or system.

4

Review and publish

Preview changes before they affect the live customer experience.

5

Use across Remapdb

Apply data to tuning widget flows, API output, AI integrations where supported, quote logic, and future modules.

Early access interest

Tell us what you need to customise

Register interest with your business context so the most important vehicle tuning database control workflows are prioritized for product planning.

Useful details to include

  • Business type and operating model
  • Whether you already have your own database
  • Data format and source system
  • What you want to edit or override
  • Whether you need widget output, API output, or both
  • Dealer-specific logic requirements
  • Custom services and pricing requirements
Coming soon

Roadmap planning in progress

This does not mean the feature is live today. It helps us prioritize the use cases with highest business value.

FAQ

Questions about Customisations

Is Customisations available now?

No. Customisations is a planned future Remapdb feature and is not live yet.

What is Customisations designed to do?

The planned direction is custom vehicle tuning database control: editing records, adjusting tuning parameters, uploading data, and managing output across widget and API surfaces.

Will we be able to upload our own database?

That is the planned direction. Structured import workflows are part of the intended scope.

Will we be able to override Remapdb data?

Yes, the intended model is Remapdb maintained data as a base with business-specific overrides.

Will custom data work in the widget?

That is the goal where supported: customised records powering customer-facing widget flows.

Will custom data work through the API?

For advanced customers, the intended direction is custom-data support through API workflows where supported.

Will custom data work with AI integrations?

The intended advanced path is for controlled custom data to support API-driven and AI-assisted workflows where supported after feature rollout.

Who is this for?

Teams needing deeper tuning-data control, custom records, and output aligned to their own file-spec standards and workflows.

Will it be in every plan?

Final packaging is not defined yet. As an advanced capability, it will likely be paid-plan or add-on aligned.

Can we register interest before launch?

Yes. Registering interest helps prioritize the workflows that matter most.

Coming soon

Want deeper control over your Remapdb tuning-data layer?

Start with today's tuning widget, remap database API, AI integrations, WordPress plugin, and support workflows, then tell us what custom database control your business needs next.