Question 1

What is Zayos?

Accepted Answer

Zayos is direct online ordering for restaurants. It replaces 25-30% commissions on DoorDash, Uber Eats, and Grubhub with orders placed straight on the restaurant's own website. Each restaurant gets a branded ordering site, a kitchen tablet, a unified inbox for direct + marketplace orders, and a per-tenant customer database. Built by Zay Revenue Group LLC.

Question 2

How does Zayos compare to Owner.com?

Accepted Answer

Both pitch direct online ordering. Zayos is the customized, customer-first alternative: every restaurant gets its own colors, logo, menu rhythm, loyalty rules, and surcharge model, not a template with theme variables. Pricing is public ($499 to $699 per month per location), there are no per-order commissions, and customer service is phone + WhatsApp with the founder responding, not a ticket queue. Multi-brand under one org is built in, not an add-on.

Question 3

How much does Zayos cost?

Accepted Answer

$499/mo per location on Operator. $599/mo per location on Operator + Marketplace (adds Otter, dispatch, AI broadcasts). $699/mo flat covers up to 5 brands or locations on Concierge (white-glove). Setup fees from $699 per location. The AI grader at grader.zayrev.com is free and requires no credit card. Zayos does not take a commission on orders or tips.

Question 4

Do I have to switch off DoorDash to use Zayos?

Accepted Answer

No. Zayos sits alongside DoorDash, Uber Eats, and Grubhub. Marketplace orders keep flowing through your existing channels (piped into the same inbox via Otter). Direct orders are an additional channel — the most profitable one because there's no commission.

Question 5

What if my POS is something old or weird?

Accepted Answer

Zayos integrates with Otter, which supports 25+ POS systems including ones nobody else does (Brink, Revel, Heartland Restaurant). If your POS is truly exotic, the Concierge tier sets up a tablet-based workflow as a fallback. You won't be left out.

Question 6

Will my kitchen staff need training?

Accepted Answer

The kitchen tablet has one screen with four columns: Accept · Preparing · Ready · Handed off. Most kitchens are fluent in about 10 minutes. The Concierge tier includes a remote training session if you want a human walking your line cooks through it.

Question 7

Can I run multiple brands from one kitchen?

Accepted Answer

Yes — multi-brand at one location is the original reason Zayos exists. Each brand gets its own subdomain, its own colors, its own customer database, and its own kitchen-tablet route. Ghost kitchens are first-class citizens.

Question 8

What if Zayos can't deliver in my zip code?

Accepted Answer

Otter's dispatch network covers most of the US. If your zip code falls outside, we hand off to your existing courier or your in-house drivers — same workflow, different fulfillment. Confirm coverage before signing.

Question 9

Who runs Zayos?

Accepted Answer

Zayos is built by Zay Revenue Group LLC, founded by Abdallah Alyousef (CEO). Headquartered in Fort Lauderdale, FL. Reach out at hello@zayrev.com or +1 (321) 666-1102.

Provider	Role	Region	DPA
Supabase Postgres database, magic-link authentication, file storage (menu photos, brand logos, media library). All customer and operator data, hashed credentials, file metadata.	Database + Auth + Storage	United States (AWS us-east region)	DPA →
Vercel Runs the Next.js application across our four projects (marketing, storefront, admin, operator). Request/response logs, IP addresses, error traces.	Application hosting + edge	Global (edge); USA primary	DPA →
Cloudflare Domain resolution, edge CDN, layer-7 DDoS + WAF. IP addresses, request metadata.	DNS + CDN + bot mitigation	Global	DPA →
Stripe Card processing for customer orders; per-tenant Connect account flows funds to the restaurant. Card tokens, billing addresses, transaction metadata (never raw PAN).	Payments + payouts (Stripe Connect)	United States	DPA →
Resend Magic-link emails, password reset, order receipts, review-request emails, customer survey invites, owner invitations. Recipient email, email body, delivery status.	Transactional email	United States	DPA →
Twilio Order status SMS (received / ready / delivered), one-time passwords for customer auth. Recipient phone, message body, delivery status.	Transactional SMS	United States	DPA →
Anthropic AI shift briefing, menu-item description generation, menu photo critique, review-response drafting, support-ticket triage, invoice OCR, PDF menu import. Operator-submitted text + images; never customer payment data.	AI model API (Claude)	United States	DPA →
Google (Places + Business Profile) AI restaurant audit autocomplete, nearby competitor lookup, Google review polling for the operator inbox, eventual response posting. Operator-supplied place IDs; public business data returned by Google.	Business data + review polling	United States	DPA →
Inngest Scheduled crons (Google review polling, expire stale announcements, post-delivery survey send, retention sweeps). Job metadata; minimal payload (org IDs, order IDs).	Durable job queue	United States	DPA →
Otter When a tenant connects Otter, we receive marketplace order events (DoorDash, Uber Eats, Grubhub) + 86-list state + payout reports. Order data, fulfillment events, payout amounts.	POS + marketplace integration	United States	DPA →
Sentry Captures unhandled exceptions + performance traces from our four Vercel projects. Stack traces, request metadata; we redact PII before send.	Error monitoring	United States	DPA →

Provider	Role	Region	DPA
Supabase Postgres database, magic-link authentication, file storage (menu photos, brand logos, media library). All customer and operator data, hashed credentials, file metadata.	Database + Auth + Storage	United States (AWS us-east region)	DPA →
Vercel Runs the Next.js application across our four projects (marketing, storefront, admin, operator). Request/response logs, IP addresses, error traces.	Application hosting + edge	Global (edge); USA primary	DPA →
Cloudflare Domain resolution, edge CDN, layer-7 DDoS + WAF. IP addresses, request metadata.	DNS + CDN + bot mitigation	Global	DPA →
Stripe Card processing for customer orders; per-tenant Connect account flows funds to the restaurant. Card tokens, billing addresses, transaction metadata (never raw PAN).	Payments + payouts (Stripe Connect)	United States	DPA →
Resend Magic-link emails, password reset, order receipts, review-request emails, customer survey invites, owner invitations. Recipient email, email body, delivery status.	Transactional email	United States	DPA →
Twilio Order status SMS (received / ready / delivered), one-time passwords for customer auth. Recipient phone, message body, delivery status.	Transactional SMS	United States	DPA →
Anthropic AI shift briefing, menu-item description generation, menu photo critique, review-response drafting, support-ticket triage, invoice OCR, PDF menu import. Operator-submitted text + images; never customer payment data.	AI model API (Claude)	United States	DPA →
Google (Places + Business Profile) AI restaurant audit autocomplete, nearby competitor lookup, Google review polling for the operator inbox, eventual response posting. Operator-supplied place IDs; public business data returned by Google.	Business data + review polling	United States	DPA →
Inngest Scheduled crons (Google review polling, expire stale announcements, post-delivery survey send, retention sweeps). Job metadata; minimal payload (org IDs, order IDs).	Durable job queue	United States	DPA →
Otter When a tenant connects Otter, we receive marketplace order events (DoorDash, Uber Eats, Grubhub) + 86-list state + payout reports. Order data, fulfillment events, payout amounts.	POS + marketplace integration	United States	DPA →
Sentry Captures unhandled exceptions + performance traces from our four Vercel projects. Stack traces, request metadata; we redact PII before send.	Error monitoring	United States	DPA →

Sub-processors

Notification of changes

Questions

Sub-processors

Notification of changes

Questions