Two teams can need a Drupal website and be at very different starting points.
One has a working site, a development partner, and a codebase it wants to keep using. The other has a clear idea of the website it needs, but no software foundation or person responsible for building one.
Both need hosting. They need different things before they get there.
Drupito gives those teams two starting points: bring your own Drupal codebase, or choose a marketplace website built on a codebase maintained by someone else. Here’s how to think through that choice.
Start with what you already have
If you have an existing Drupal project, begin by asking whether its foundation still fits your needs.
Does the site support the way your team publishes? Do your custom features still matter? Do you have someone who understands the code and can maintain it?
If the answers are yes, bringing your own codebase may be the useful path to explore. You’re evaluating a new hosting arrangement for work you want to keep using.
If you’re unhappy with the site itself, take a closer look at why. A hosting change and a redesign solve different problems. Slow editorial workflows, confusing navigation, and outdated content structures deserve their own decisions, even if you also plan to move hosts.
Look at foundations through everyday tasks
If you’re starting fresh, a marketplace website gives you something concrete to evaluate.
Begin with the work your site needs to support. For a nonprofit, that might include explaining a program, keeping event details current, and directing visitors to a donation service. For a training business, it might mean presenting courses clearly and helping prospective students take the next step.
Those are requirements to check against a particular listing. Explore its demo, available features, maintenance scope, and costs. Notice what fits immediately and what would require additional work.
A useful starting point should make your important tasks easier to picture. A long feature list only helps when those features serve your organization.
Decide who will maintain the code
This is one of the most consequential differences between the two paths.
When you bring your own codebase, maintaining that code remains a responsibility for your team or development partner. Managed hosting gives the project a place to run; clarify the hosting service’s scope separately.
When you choose a marketplace website built on a maintained codebase, someone else maintains the underlying foundation. Review the particular offering to understand what that includes. Ask how updates reach your website and what happens if you add custom code or integrations.
In either case, your organization still needs someone to own its content, users, and visitor experience.
Compare the complete arrangement
Before choosing, write down four things:
- What you’re starting with: an existing codebase or a marketplace website.
- Who maintains the underlying code and any custom additions.
- What the plan includes, how it is billed, and what could add cost.
- What needs to happen before your website can go live.
This small exercise turns a broad platform comparison into a decision about your actual project.