Planned, not live yet
Customisations is currently in roadmap planning and not available inside the product today.
Customisations - coming soon
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.
Customisations is currently in roadmap planning and not available inside the product today.
Available now
Widget, dealer locator map, WordPress plugin, API options, quoting, branding, pricing controls, and support are live today.
Best next step
Tell us which data-control workflows matter most so roadmap priorities reflect real demand.
Planned capabilities
Customisations is planned for teams that need deeper control over records, values, and output logic while keeping one operational data layer inside Remapdb.
Modify vehicle, model, engine, ECU, stage, and customer-facing tuning-data fields where supported.
Adjust stock and tuned power, torque, kW, gains, stage values, ECU file-spec notes, and display logic.
Import structured vehicle tuning database records and manage them from one control layer.
Add vehicles, engines, variants, services, notes, and business-specific internal data.
Use Remapdb maintained data as a base, then apply your own corrections and custom logic.
Use customised records in tuning widget flows, remap database API workflows, quote forms, AI integrations where supported, and future modules.
Why it matters
Advanced teams often need their own tested tuning values, compatibility notes, and business-specific data standards reflected in customer-facing journeys.
Control the data your customers see and keep output aligned with your standards.
Manage services, pricing, and dealer-specific data behavior with deeper precision.
Connect your own file-service catalogue, ECU file specs, and records to the customer journey.
Use custom vehicle tuning database data in dashboards, portals, API workflows, and internal operations.
Manage compatibility and performance records tied to product-led journeys.
How it may work
Final implementation may evolve, but the intended workflow stays straightforward and operational.
Use the maintained vehicle tuning database as your foundation.
Adjust vehicles, engines, stages, values, notes, and key fields.
Import structured data from your own catalogue or system.
Preview changes before they affect the live customer experience.
Apply data to tuning widget flows, API output, AI integrations where supported, quote logic, and future modules.
Early access interest
Register interest with your business context so the most important vehicle tuning database control workflows are prioritized for product planning.
This does not mean the feature is live today. It helps us prioritize the use cases with highest business value.
Start with today's products
Add vehicle lookup, tuning gains, services, pricing context, and quote requests with a tuning widget for website pages today.
Explore widgetUse remap database API and ECU tuning data API access in your own dashboard, portal, custom product, or workflow.
Explore APIUse AI integrations through the MCP server when supported assistants need structured access to Remapdb vehicle tuning database data.
Explore AI integrationsUse the plugin for a dedicated WordPress tuning-data installation path.
View WordPress pluginGet setup help, documentation access, and product guidance.
View supportCompare plans for current features, API access, branding, and support.
See pricingFAQ
No. Customisations is a planned future Remapdb feature and is not live yet.
The planned direction is custom vehicle tuning database control: editing records, adjusting tuning parameters, uploading data, and managing output across widget and API surfaces.
That is the planned direction. Structured import workflows are part of the intended scope.
Yes, the intended model is Remapdb maintained data as a base with business-specific overrides.
That is the goal where supported: customised records powering customer-facing widget flows.
For advanced customers, the intended direction is custom-data support through API workflows where supported.
The intended advanced path is for controlled custom data to support API-driven and AI-assisted workflows where supported after feature rollout.
Teams needing deeper tuning-data control, custom records, and output aligned to their own file-spec standards and workflows.
Final packaging is not defined yet. As an advanced capability, it will likely be paid-plan or add-on aligned.
Yes. Registering interest helps prioritize the workflows that matter most.
Coming soon
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.
Customisations is planned for advanced vehicle tuning database control and workflow-specific output.