Who can use this: Everyone URL / Route: n/a (concept page)
Solavel in one line
Solavel is a business operating platform — a single account, a single bill, and a growing family of apps that run on top of one shared workspace. Sign in once, pick the apps your team needs, and switch between them without re-logging in or re-importing data.
How the platform is organised
Think of Solavel in three layers.
| Layer | What lives there | Why it matters |
|---|---|---|
| The platform | Your account, your team, your organizations, your billing, your plan. | One identity and one bill across every app you ever turn on. |
| The apps | Specialised products you turn on per organization (today: Solabooks for accounting, with more in the catalogue and more on the way). | Pay only for what you use; switch new apps on without standing up a new login or paying a new vendor. |
| The customer touchpoints | Secure document links, customer portal, accept-quote pages. | Lets your customers receive invoices, approve quotes and access shared work without needing a Solavel account. |
This is the same model used by every modern multi-product SaaS — Google Workspace, Microsoft 365, Zoho One. You don't shop for a separate accounting login and a separate project login; you sign into the platform and switch contexts.
The current app catalogue
Solavel is built to host many apps. The catalogue grows with every release; what's live in this build:
- Solabooks — Accounting & finance. Invoices, bills, banking, taxes, fixed assets, multi-currency, multi-org reporting, customer portal, secure document links. Available now.
- Solavel Projects. Project management, time tracking, customer-facing time approvals. Wired into the platform; surfaces inside Solabooks today.
- HR module. People, employees, leave. Available as a separately-priced add-on per organization.
- Inventory module. Stock, reorder points, low-stock alerts. Available as an add-on or bundled with Solabooks.
What's coming is bigger than what's live. The platform is designed for scale: each new app reuses the same login, the same billing, the same organizations, the same support — so adding a new product never means starting over.
What ties everything together
These four pillars are why Solavel is a platform and not "a couple of apps":
- One identity. Sign in at
solavel.comonce. Every app you have access to opens without another login. Sign out of any app and your session ends across the platform. - One bill. Every subscription — every app, every plan tier, every add-on — is paid through the central billing screen. One card, one VAT receipt, one billing cycle.
- One workspace model. Your team, roles and customers are defined at the organization level. Every app respects the same org, the same members, the same permissions. Onboard a customer once; they're available in every app you switch on.
- One support and operations layer. System events, error reports, audit logs and the support playbook span every app. When something goes wrong, you don't bounce between vendors.
The vocabulary you'll see
Organization. A workspace owned by a client. Each organization has its own billing, its own plan, its own members, and its own private database for data-heavy apps like Solabooks. A user can belong to many organizations.
Client. The legal entity (company or person) that pays the bills. One client can own several organizations.
App. A product that an organization can switch on. Examples: Solabooks, Projects, HR, Inventory. Apps have their own pricing tiers and feature flags.
Plan tier. The pricing level you pick for a given app — typically Free, Professional, Premium, Enterprise — each with different limits and feature toggles.
Bundle. A pre-priced combination of apps (e.g. Starter, Business, Enterprise) that lets you turn several apps on at one tier with one price.
Subscription. The active link between an organization and a plan tier or bundle.
Member. A user inside an organization. Members have a role (owner / manager / member / approver / accountant) that decides what they can do.
How users move between apps
- Sign in at
https://solavel.com/login. You land on the central dashboard. - Pick or create an organization from Organizations.
- Open an app (e.g. Solabooks) from the launcher. The platform hands you over with a short-lived signed token; the app verifies it and starts your session — no second login.
- Switch back to the platform any time by visiting
https://solavel.com/dashboard.
Sign out anywhere and the platform signs you out of every connected app.
Where billing lives
All billing happens at the platform level — never inside an individual app.
- Customer-facing billing screens:
/portal/orgs/{organization}/billing/*. - Change a plan:
/portal/orgs/{organization}/plan. - Card payments are handled by the Tap payment gateway.
If an app shows you a "Plan does not include this feature" screen, the upgrade link sends you back to the platform's plan page. Apps never collect payment directly.
Where data lives
Each organization has its own private database for apps that hold operational data (Solabooks is the obvious example). The platform itself owns a single shared database for users, clients, organizations, subscriptions, invoices, audit logs and feature flags. Two organizations on the same platform never see each other's data — they're physically separated.
Why one platform instead of separate vendors
- No duplicate logins. Add five apps; still one password.
- No duplicate customer lists. Onboard a customer in Solabooks today; they're available in Projects tomorrow.
- No duplicate billing. One invoice from Solavel, every month, regardless of how many apps and bundles you run.
- No vendor sprawl. When something breaks, one support team, one log, one audit trail covers it.