The short version
You can start with hosted clinic software and revisit self-hosting when your practice needs more control over how the system runs.
- Hosted SaaS: 7DaysCare runs the hosting environment, so you can focus on getting your team set up.
- Self-hosted: choose where the platform runs and tailor it to your workflows. Your team or a partner takes on the work of running it.
- Provider choice: with the applicable ownership licence, your organization can have its own team or another supplier maintain covered modules.
Hosted vs. self-hosted clinic software
If you’re choosing software for a practice, start with a question you can answer without talking about servers: what do you want your team to spend time on? A solo therapist may want to get started quickly. A clinic with several locations might care more about how staff permissions, reporting and integrations work across the group.
Both options build on the same 7DaysCare platform. With the hosted service, 7DaysCare operates the hosting environment and you use the application. With the self-hosted option for clinics and organizations, the platform runs on your own server or in a dedicated environment. You can have more say in the setup, and you’ll need to decide who keeps it running day to day.
Self-hosting can make sense when you have a clear requirement for it. If your needs are still taking shape, give yourself time to learn from the way staff actually use the software. The things that slow people down in a normal week are often a better guide than a feature checklist.
When hosted SaaS is a good fit
Imagine you’re opening a small practice and doing most of the setup yourself. You’d rather spend your first week getting your schedule and team access sorted than arranging a server. A hosted service gives you a way to start there. The 7DaysCare page for therapists explains how the hosted offer fits a practitioner’s day-to-day work.
Try a few everyday tasks during your evaluation. Ask the person who manages bookings to run through an appointment change, and have a new team member sign in with the permissions they’ll actually need. If the standard setup handles those tasks well, you have a practical reason to choose it. If there’s a gap, write down how often it happens and who it affects.
Before you pick a package, ask how support works and what’s included. Find out who manages user access, how to request an export and what happens to your records if you leave the service. Put the answers somewhere your team can find them later, when the person who set up the account might be away.
When a customized deployment makes sense
Say you run several clinics and each location needs a different approval process. Or perhaps your team has to enter the same information twice because two systems don’t talk to each other. These are examples of problems worth describing in detail when you’re considering a custom deployment. Ask whether existing settings can do the job before paying for new code.
A dedicated deployment also gives you more control over where the software runs and when you make changes. That control comes with regular work. Someone needs to monitor the service, apply updates, check backups and make sure the team can recover from an outage. If you hire a provider, ask who to call on a busy morning when staff can’t sign in.
When you compare costs, use the same time period for both options. For hosted, list the package, setup and any extras you need. For self-hosted, include the licence, migration, development, infrastructure and ongoing support. Include the time your own team will spend on each option. That’s often the cost that’s hardest to see in a quote.
How to move from hosted to self-hosted
You can start hosted and come back to this decision later. If you do move, give yourself time to work through these four steps before booking a changeover date.
Write down what needs to change
Pick two or three examples from an ordinary working week. Maybe staff at different locations need different access, or someone copies the same information into another system every Friday. Show what happens today and what you’d like to happen instead. Use those examples to decide whether a configuration change would help or whether you need custom development.
Find out what can come with you
Make a list of the records, files, settings and integrations your team uses. Ask which items can transfer, which formats are available and which pieces need to be rebuilt. Include details people may forget, such as attachments, historical records and user permissions. Ask who will check that the information is complete in the new system.
Give every task an owner
Write down who will run the environment, apply updates, check backups and help staff when something breaks. Give each task a named owner and a backup contact. If you work with two suppliers, agree who takes the first call and how they’ll work together when a problem crosses between systems.
Rehearse before you switch
Give the people who do the work a chance to try the new setup. Ask them to walk through typical tasks, check that they have the right access and flag anything that takes longer than expected. Agree what would make you postpone the switch and how your practice would keep working in the meantime.
Bring your team into the planning
Walk through the proposed setup with the people who will use it. Their day-to-day experience can help you spot missing steps before a change goes live.

Build your own team around Odoo Community
7DaysCare is based on Odoo ERP 20 Community. Depending on the modules and configuration you choose, that foundation can support internal operations such as team administration, procurement and inventory alongside care workflows. The Odoo 20 administration documentation describes the Community edition and its administration options.
If you want to bring some of the work in house, start with the skills you already have. A practice manager may know exactly what a new workflow should do, while an Odoo developer can work out how to build it and keep it working through upgrades. Give both people a say in what gets built and how you’ll know it works.
The applicable 7DaysCare ownership licence can give you access to the source for covered modules and the option to bring in another provider. Ask what’s included in writing. A useful handover covers the repository, installation instructions, dependencies and who controls access to the hosting environment. If a future maintainer can tell what’s running and how to make a change, you’ll have a much easier time handing the work over.
What to learn in your first month
If you start hosted, keep a short list of the workarounds people use. Ask the person at reception what takes too many clicks. Ask the practice manager which reports need cleaning up before they can use them. Ask a new colleague where they got stuck during setup. Give each issue a real example, how often it happens and the time it costs. At the end of the month, sort the list into training, settings and changes that might need development.
For example, imagine two locations produce different versions of the same weekly report. Before asking for a custom report, agree on what each column means and whether both teams record information the same way. Try the simplest workflow everyone can follow. If you still need to combine data by hand, you now have a clear brief: which fields to combine, who needs the result and when they need it.
You can also prepare for a future move while you’re still happy with the hosted service. Keep a record of who approves access, which tools are connected and where your team stores its operating instructions. Ask what a sample export looks like and who can request one. These details are easier to collect during a normal week than during a changeover.
Set a date to revisit the decision with the people who use the system. Bring the list of recurring problems and ask which ones affect care or cost staff the most time. If a different setup would solve them, take those examples into a discussion with your provider. If a training session or a change in settings is enough, you can make that change sooner. Either way, your team has a clearer picture of what it needs from the software.
What to confirm before choosing
- Scope: Which workflows come with the package, and which would need configuration or development?
- Costs: What would we pay to get started, and what would we spend each year to keep it running?
- Data: What can we export, how do we get it and who checks that backups can be restored?
- Support: Who takes the first call when staff need help, and who looks after the infrastructure?
- Handover: Which source code, development rights and documentation would we receive?
Frequently asked questions
Can I start with hosted 7DaysCare and move later?
Yes. 7DaysCare offers hosted and self-hosted options based on the same platform. If you decide to move, discuss the scope with the team. Ask which data and settings can transfer, which work needs to be quoted and how you’ll check the new setup before the switch.
Does self-hosted mean I need a server in the clinic?
No. The self-hosted option can use your organization’s server or a dedicated environment. Ask where the system and backups would run, who can access them and which team would respond if the service went down.
Who handles updates and backups?
For a self-hosted deployment, agree who will apply updates, check backups and handle recovery. That can be your internal team or a partner. For the hosted service, ask what the package covers and what your practice still needs to manage, such as staff access.
Can our team customize 7DaysCare or bring in another provider?
Your organization can arrange for an internal team or another supplier to maintain covered modules under the applicable ownership licence. Before making a decision, confirm the source code, rights, dependencies and handover support included in your agreement.
Does Odoo Community make every 7DaysCare module open source?
Odoo Community is the open source foundation. Additional modules, connectors and services can have their own terms. Ask for a list of the components in your proposed deployment and check the rights for each one you may need to modify.
Where can I find pricing for both options?
Start with the hosted pricing page to explore packages. If you’re considering a self-hosted setup, ask 7DaysCare for a quote that covers the licence, implementation, migration and support you need. Budget separately for any infrastructure or work your team will provide.
Sources and further reading
Find the right setup for your practice
If the hosted service meets your needs today, start there. If you already know which workflows or integrations need more control, bring those examples to a conversation about self-hosting. Tell us what your team needs to do on a typical day and we can help you compare the two options.

