Three products. One way of building software.
Tenvia Coworks, Tenvia Build and Tenvia PM are separate applications for separate industries. What they share is the architecture underneath: how your data is kept apart from everyone else's, who can see what, where it lives, and what happens when you want it back.
Independent products on one foundation.
One application per industry
Each product is its own application with its own database. A coworking operator and a contractor never share a system, a codebase or a table. Nothing you do in one product can affect another.
Your business is a tenant
Inside a product, every business operates in its own tenant. Records are scoped to the tenant that owns them at the data layer, not just hidden in the interface, so a query for your data can only return your data.
Clients inside your tenant
Your clients, members or owners get their own portal. Their access is scoped again, to their records within your business, so a portal user sees their bookings and invoices and nothing else.
Roles decide what staff see
Access is granted by role. Permissions decide what is visible and what can be changed. Multi-location operators scope staff to individual sites. Staff users are unlimited on every tier of every product.
Every change is on record
User actions and record changes are logged. When something looks wrong you can see who did what and when, without asking us to dig through a database.
One design, not one login
The products share a design system and the way they are operated, so a team that runs two of them learns one set of habits. They do not share accounts or data.
Hosted in Canada, on infrastructure you have heard of.
Every TenviaOS product runs on Amazon Web Services in the Canada (Central) region, on managed PostgreSQL databases with automated backups and encryption at rest. Traffic is encrypted in transit. There is no shared database between products, and no back door from one product into another's data.
Card numbers never land in the platform. Payment methods are held as processor tokens with Stripe, so a card is charged without any TenviaOS system ever storing it.
Documents are access-controlled against the record they belong to rather than by a shared folder, so a file attached to a project or a lease is reachable only by people who can see that project or lease.
Why we build it this way.
Finished for the industry, not generic
A product that only has to serve one industry can model that industry properly: change orders in Build, virtual mail in Coworks, units and leases in PM. A general tool would have to compromise on all three.
No bundle, no lock-in between products
You buy the product you need and only that. If you later run a second business in another industry, you buy that product on its own terms, and the two stay separate.
Built for the operator
The primary user is the person running the business day to day. Software that needs a consultant to switch on has already failed that person, so setup is something you do yourself.
Your records are yours
Everything you put in can be exported at any time. Cancelling does not hold your data hostage: you keep access until the end of the paid term and can take an export before you go.
Built to be left running
Reliability and clear records matter more than novelty in systems businesses depend on. Releases are small and frequent; nothing is rebuilt from scratch under you.
Honest about certifications
We are not SOC 2 certified today and we will not imply otherwise. The practices above are how the platforms are built; the paperwork follows when the business is ready for it. Read the security page for the detail and how to report an issue.
Each product is priced on its own.
Three tiers on every product, Starter, Growth and Scale, priced for that industry. Prices live on each product's own page.