1
Portfolio command center
See properties, units, occupancy, rent, and operational health from one place without losing the details.
Launch-ready • private trials • manual provisioning today
One calm command layer for property ops.
Tenaro gives operators one calm command layer for leases, maintenance, vendors, and payments — then provisions each customer instance deliberately, not sloppily.
Dedicated, not shared
Every pilot is framed as its own instance so the eventual handoff to manual provisioning stays clean.
Built for real workflows
Owners, tenants, vendors, maintenance, payments, and lease ops live in one place.
Secure by default
Teal-on-navy brand, role-based access, and a launch path that does not overpromise automation.
Request your private trial
We review each request, provision the instance manually, and keep the handoff tight. No self-serve wizard to break things.
Platform fit
What Tenaro is for
Built for property operators who want a tidy operational system instead of a pile of disconnected tools and spreadsheets.
2
Leases, payments, and reporting
Keep the financial and document trail attached to the right unit, lease, and tenant record.
3
Maintenance and vendors
Route requests, assign vendors, and track job status with a practical audit trail.
4
Role-based portals
Owners, tenants, and vendors each get the view they need, not a giant generic dashboard.
Who this fits
Tenaro is a good fit for owner-operators, smaller teams, and growing portfolios that need a professional system before they need enterprise bloat.
- Single-owner portfolios that want one calm home base.
- Teams juggling tenants, maintenance vendors, and rent collection.
- Operators who want manual onboarding now and automation later.
What the trial means
Right now, a trial request is a lead for a dedicated Tenaro instance. We review it, provision the environment manually, and follow up with the next step instead of pretending there is a one-click signup that does not exist yet.
- No card required for the initial review.
- Each request is stored and tracked as its own lead.
- Manual provisioning keeps v1 safe and launchable.
How it works
Private trial flow
Simple enough to convert, honest enough to ship.
1. Request the trial
Share the basics: who you are, portfolio size, timeline, and what you want to solve. The form writes to the machine in a durable SQLite table.
2. Review and provision manually
The lead is visible to the admin workflow. We can mark it as reviewed, approved, or provisioned once the instance is created.
3. Invite the right people
Once the instance exists, we can create the first owner account and onboard tenants, vendors, or managers in a controlled way.
4. Tighten the loop for v2
When automated provisioning is worth it, we add templates, queues, DNS, secrets, billing, and instance lifecycle tooling.
Pricing & trial framing
Private pilot first, public pricing later
For v1, the honest offer is a private trial with manual setup. That keeps the launch tasteful and avoids fake self-serve promises.
Founding pilot
Private trial, manual provisioning, onboarding help, and direct follow-up. This is the right shape for the first real customer conversation.
No public signup funnel theater
No card for the review step
Dedicated instance framing
What gets unlocked next
Once the demand is real, the next pricing layer can be tied to the provisioning model rather than guessed at today.
- Self-serve instance creation after the provisioning engine exists.
- Optional onboarding fee or setup charge if the market wants it.
- Clear package tiers by portfolio size and support level.
Trust / FAQ
Questions people will actually ask
Is this a shared demo environment?
No. The positioning is private instance first. We collect leads, review them, and provision the workspace deliberately instead of stuffing everyone into one sandbox.
How fast do you follow up?
The target is one business day for the initial review. Because setup is manual in v1, follow-up is human and honest.
Can we start with a small portfolio?
Yes. The form asks for portfolio size because a small pilot is often the right way to validate the fit before scaling.
When does real self-serve provisioning arrive?
That is a v2 project. It needs templates, a queue, secrets handling, per-instance config, DNS automation, billing hooks, and admin tooling. Better to build that once the demand is proven.