Key facts
| API compatibility | OpenAI-compatible chat, embeddings and function calling |
| Use cases | Maintenance ticket triage, lease Q&A, tenant and vendor message drafts, listing copy |
| Data controls | API keys, RBAC, SSO, audit logs and region selection |
| RAG | Index lease and policy documents so answers cite the source clause |
| Deployment | Plugsky cloud, your VPC, on-prem and air-gapped options |
| Models | 30+ models from free aliases to frontier reasoning |
| Pricing model | Flat monthly self-serve plans with unlimited fair-use usage |
| Free tier | plugsky-micro and plugsky-lite on the free plan, no card required |
TL;DR
- Classify and route maintenance tickets before a human reads them.
- Answer lease questions with citations to the clause, not model memory.
- Draft tenant and vendor replies; keep a manager in the send path.
- Scope keys and review audit logs wherever tenant data is involved.
- Start free, then compare models on ticket accuracy and response time.
How it works, step by step
- Start with ticket triage: classify category, urgency and likely trade from the resident's text.
- Index the lease, house rules and maintenance policy so Q&A can cite the governing clause.
- Draft replies and work orders, and route them to a property manager for approval.
- Scope API keys per integration (portal, inbox, work-order tool) and turn on audit logs.
- Set the processing region and retention to match your tenant privacy commitments.
- Measure routing accuracy and first-response time, then extend to vendor quote summaries.
Try it yourself
Open the RAG architecture builder →
Practical use cases for property teams
Property management is a high-volume, document-heavy service business, which suits narrow AI tasks:
- Ticket triage: read a resident message, classify the issue and route it to the right trade with an urgency label.
- Lease Q&A: answer questions about notice periods, pets or parking with a citation to the relevant clause.
- Reply drafting: generate a first response in your tone, ready for a manager to edit and send.
- Listing and notice copy: produce consistent descriptions and notices from structured unit data.
Keep approval with staff for anything that commits the owner or the tenant.
Security and tenant data
The sensitive material is tenant identity, payment history, maintenance access details and owner financials. Configure scoped API keys per integration, RBAC and SSO for staff, and audit logs so each request is attributable. Choose the processing region and set retention deliberately, and exclude payment credentials from prompts entirely. Where the portfolio or a client contract requires it, isolate at the deployment level with a VPC or on-prem install rather than sharing a public tenancy. Plugsky provides these controls; the property's privacy policy still governs what you may send.
Architecture that scales across a portfolio
A practical stack is an inbox or portal webhook, a classification call for triage, a retrieval index for lease and policy Q&A, and a drafting call that writes into your existing work-order tool. Because Plugsky is OpenAI-compatible, the same code runs in the cloud, in your VPC or on-prem. Index documents per property or per owner if confidentiality requires separation, and keep a stable id for every clause so citations resolve. Use plugsky-embed for retrieval and a stronger model only for the final draft.
Getting started
Prototype on plugsky-micro or plugsky-lite with one property's ticket backlog. Label a few hundred tickets, measure routing accuracy, then use the 14-day full-access trial to test frontier models on the hardest cases. Self-serve plans are flat monthly with fair-use usage, so cost per unit does not swing with ticket volume. Track first-response time and misroutes, keep prompts versioned, and add a second workflow only when the first is stable.
Honest comparison
| Capability | Plugsky | Typical per-token API | Building in-house |
|---|---|---|---|
| API compatibility | OpenAI-compatible chat, embeddings and tools | Usually compatible | Full rewrite |
| Access control | Scoped API keys, RBAC, SSO and audit logs | Varies by provider | You build all of it |
| Deployment | Cloud, VPC, on-prem and air-gapped | Mostly cloud-only | You operate GPUs and serving |
| Pricing | Flat monthly self-serve, fair-use usage | Per-token, harder to forecast | GPU plus operations cost |
| Model choice | 30+ models behind one API | Varies by provider | You host every model |
Frequently asked questions
Can we keep our existing OpenAI SDK code?
Yes. Plugsky is OpenAI-compatible, so you change the base URL and model name and keep your existing SDK and integrations.
Is there a free plan?
Yes. The free plan includes plugsky-micro and plugsky-lite with no credit card, enough to prototype ticket triage and lease Q&A.
Can the model send messages to tenants directly?
It can draft them, but keep a property manager in the approval path for anything that commits the owner or tenant or shares account details.
How do we handle lease questions accurately?
Index the lease and policy documents with embeddings, retrieve the relevant clauses, and require citations in the answer so staff can verify the source.
How does pricing work?
Self-serve plans are flat monthly with unlimited fair-use usage. See the live pricing page for current plans and enterprise options.
Can we deploy in our own environment?
Yes. VPC, on-prem and air-gapped options are available for portfolios or clients that restrict where data is processed.
Which endpoints are live today?
Chat, streaming, JSON mode, function calling, embeddings, RAG and agents are live. Audio, images, moderation, files, batch, fine-tuning, assistants and responses are coming soon.