Custom development

Custom features that survive updates

Your AI team builds new features and new designs right in your admin panel. Architecture changes go to the platform's development team.

Three paths

Who builds it depends on how deep the change goes

AI team

New features and new design

Your AI team builds custom work right in your admin panel: a new integration, a custom field, the payment gateway your market uses, a new design. The result is a standard add-on or theme that survives platform updates.

Cost
Included in your service period. Models run on your own AI account
Support
Your AI team fixes and updates their own add-on while your service period is active
Tamaranga team

Architecture changes

For changes to how existing parts of the platform behave. Our team builds the change into the product itself, in the core or as an official add-on.

Cost
Invoiced. We agree on the spec, price, and timeline up front
Support
Covered by standard platform updates
Web agency

Separate code for your project

A web agency with experience on the platform writes code on top of it. It works, but you pay separately for update compatibility and ongoing support.

Cost
Under your contract with the agency
Support
Paid separately and needs constant attention
AI team

How your AI team builds it

IDA (Intelligent Domain Assistance) gives your AI team your setup from day one: what you sell, your add-ons, your live data. So you can describe the task in plain words.

  1. Describe the task right in your admin panel
  2. The /dev role builds an add-on or theme
  3. You review the result. Nothing ships without your say-so
  4. The code is yours to keep, review, and change
Your AI team · /dev

You: “Add the payment gateway my market uses”

“Built. A standard add-on that survives platform updates.”
IDA · in your admin panel

Who maintains the add-on afterward

The same as with the programmer who wrote it.

While your service period is active

Your AI team fixes and updates their own add-on

Like a programmer you keep working with: if the add-on needs a fix or an update, just give that task to your AI team. They make the changes right from your admin panel.

If you don't renew your service period

The code stays yours, and the work can continue

Like a programmer who is no longer available: another developer or any AI coding agent can take over. Not as efficiently as your AI team, which already knows your project and knows how to work with Tamaranga, but it gets done.

Developer documentation
Architecture changes

The Tamaranga team or a web agency

When the task goes deeper than new features and design, a development team takes it on. Here is how the two approaches differ.

Built into the platform

With the Tamaranga team

Instead of changes that need ongoing support from an outside agency, we build the feature into the platform. Our team makes it part of the product itself. It stays compatible with updates, is supported on an ongoing basis, and needs no separate maintenance fee, because its support is part of our service.

How the process works

  1. We assess how much other customers need the feature
  2. We analyze and adapt the requirements so they work for everyone
  3. We agree on the spec, price, and timeline
  4. We build it with the whole platform architecture in mind
  5. We add the code to the core or release it as a separate add-on
  6. We test compatibility with every part of the system
  7. We document the new feature and include it in official updates
  8. We keep supporting it in standard platform updates

Custom development isn't our main focus, because every project means stepping away from the planned roadmap. But we know how much it matters for a fast launch, so we take on custom work when we can and when it can benefit everyone.

Custom project work

With an integrator

When you launch a project on a ready-made platform, you can bring in an integrator for custom work and to adapt the platform to your project. An integrator is a web agency with experience on one or more ready-made platforms, including ours.

How an agency works

  1. Analyze your requirements and project needs
  2. Plan the changes around the platform's capabilities
  3. Write and deploy custom code
  4. Create and deploy a custom design
  5. Test every change
  6. Launch the customized solution

After launch: keeping it compatible

  • Regular site checks with every platform update
  • Adapting the code to new versions
  • Documenting every custom change
  • Keeping everything working as new platform features roll out
From experience

Years of working with integrators showed us a pattern: the more custom work changes a project's architecture, the harder it is to keep it compatible with updates.

In practice you pay not only for the change itself but also for its ongoing support. And the project loses the main advantage of a ready-made platform that keeps evolving: updates to existing features and new capabilities that keep it competitive.

Compare

Three paths side by side

Criteria
AI team
Built into the platform
Web agency
Who does the work
Your AI team, in your admin panel
The platform's development team
An integrator (web agency)
Best for
New features and new design
Architecture changes to existing entities and their functions
Custom tasks for a single project
How it fits in the code
A standard add-on or theme
Added to the platform core or released as an official add-on
Separate code on top of the existing platform
Update compatibility
The add-on survives platform updates
Fully guaranteed compatibility
Can break with updates and needs extra support
Support
Your AI team during your service period. Without service, another developer or an AI coding agent
Automatic, in standard platform updates
Paid separately and needs constant attention
Cost
Included in your service period, models on your own AI account
Invoiced
Under your contract with the agency
Who gets the feature
Your project only
Every platform user
That project only
Effect on architecture
Doesn't change the architecture of existing entities
Fits naturally into the platform architecture
Can significantly change the project's architecture
Long term
The code is yours to keep developing
The feature evolves with the platform
Can go out of date or need rework
Questions

Common questions about custom development

What can the AI team do on their own, and what can't they do?

Your AI team can add new features to almost anything in the platform and create new designs: integrations, custom fields, payment gateways, new pages, and new elements.

What the AI team can't do is make deep architectural changes to the platform's existing entities and their functions. Those go to the platform's development team, built into the platform.

How much does custom work by the AI team cost?

The AI team's work is included in your service period. AI model usage is separate and billed by your provider directly to you.

Custom development that our team builds into the platform is invoiced separately.

Can I get cashback or a revenue share from an add-on I commissioned?

This applies to custom development that our team builds into the platform. The answer is no, and here is why:

  • It's part of a shared ecosystem. Everything we build becomes part of the platform, either in the core or published in our add-on catalog. We don't build or sell individual modules on a customer's behalf.
  • We cover all support costs. You don't pay for ongoing support, bug fixes, or adapting the feature to future updates. We do all of that long-term work at our own expense.
  • It affects our roadmap. We don't keep a team on standby for outside tasks. When we take on your task, we knowingly postpone planned improvements that might matter more to a wider audience. It's always a deliberate choice and a real risk on our side.
Why should I pay for a feature everyone will use?
  • You don't have to. If the task doesn't need architecture changes, start with your AI team. You can always go to a web agency too. Building into the platform takes some coordination, but over time it is more resilient and better value, thanks to built-in support and update compatibility.
  • First of all, it's an investment in your project. You need the feature to grow and earn, and we help you get it in the most convenient, supportable form.
  • You already use features that other customers requested and paid for. That's the natural part of a shared ecosystem, where everyone benefits from what others contribute.

Need a feature the platform doesn't have?

Start with your AI team in your admin panel. If the change needs architecture work, contact us and we'll come back with a spec, price, and timeline.

See how the AI team works Discuss custom development