Key facts
| API compatibility | OpenAI-compatible chat, embeddings and function calling |
| Use cases | Menu and specials copy, review responses, invoice extraction, staff procedure Q&A |
| Multi-location | Scoped keys and projects per brand, region or franchise group |
| Data controls | Audit logs, RBAC, SSO and region selection |
| 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
- Write consistent menu and specials copy across every location.
- Draft review responses in brand voice, with a manager approving each one.
- Extract line items from supplier invoices into your accounting flow.
- Give staff instant answers from the operations manual.
- Scope keys per location so one integration cannot read another's data.
How it works, step by step
- Start with menu copy from structured dish data to standardise tone across locations.
- Index the operations manual and allergen guidance so staff Q&A can cite the source.
- Extract supplier invoice line items into your accounting system for human approval.
- Create scoped API keys per location or brand and turn on audit logs.
- Exclude payment card data from prompts and keep it in your payment provider.
- Track minutes saved per task, then extend to review responses and shift briefings.
Try it yourself
Restaurant tasks worth automating
Restaurant operations run on short, repetitive text and structured data:
- Menu copy: generate consistent descriptions and allergen notes from structured dish data.
- Review responses: draft a brand-appropriate reply for a manager to review and post.
- Invoice extraction: pull supplier, date, line items and totals from invoices into accounting.
- Staff Q&A: answer procedure, opening and allergen questions from the operations manual.
Keep managers in the loop for anything public or financial.
Security and payment data
Payment card data should never enter a prompt; keep it in your payment provider and store only tokens where needed. For the rest, configure scoped API keys per location or brand, RBAC and SSO for staff accounts, and audit logs so each request has an owner. Choose the processing region and retention to match your privacy commitments, and avoid sending employee identity documents or payroll data through a general-purpose workflow. Franchise groups usually want deployment-level separation, which Plugsky supports through VPC and on-prem options.
Multi-location rollout
The API is OpenAI-compatible, so one integration can serve every location while keys keep data separate. A practical pattern: a central menu service writes copy from structured data, each location runs its own retrieval index for manual Q&A, and invoices flow through a shared extraction service that routes to the right accounting entity. Use plugsky-lite for high-volume simple tasks and a stronger model only for customer-facing copy. Stable document ids keep citations resolving when manuals are updated.
Getting started cheaply
Prototype on the free plan with plugsky-micro or plugsky-lite using one location's menu and invoices. Then use the 14-day full-access trial to test a frontier model on review responses and customer-facing copy. Track edit minutes per task, extraction error rate and staff search time. Self-serve plans are flat monthly with fair-use usage, which suits seasonal volume. Roll out location by location with versioned prompts rather than switching everything at once.
Honest comparison
| Capability | Plugsky | Typical per-token API | Building in-house |
|---|---|---|---|
| API compatibility | OpenAI-compatible chat, embeddings and tools | Usually compatible | Full rewrite |
| Multi-location | Scoped keys and projects per location | Shared key by default | You design tenancy |
| 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 current integration code.
Is there a free plan?
Yes. The free plan includes plugsky-micro and plugsky-lite with no credit card, enough to prototype menu copy and invoice extraction.
Can the AI reply to reviews automatically?
It can draft a response, but keep a manager in the approval path for anything public so tone and accuracy are checked before posting.
How do we handle multiple locations?
Use scoped API keys per location or brand, and separate retrieval indexes where manuals or data differ between sites.
Is payment data safe to send?
No. Keep payment card data in your payment provider and out of prompts entirely; send only the operational text the task needs.
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.
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.