1010 features
Security, Team & Account
Your data stays yours, your team sees only what the job needs, and a traffic spike never turns into a surprise invoice.
Row-Level Tenant Isolation
Your data cannot reach another workspace.
- What it does
- You route commercially sensitive lead data, so isolation has to be structural, not a matter of careful coding. Separation between workspaces is enforced by the database itself on every table, not only in the application.
- Why it exists
- Without it, one missing filter in one query could show your networks, prices and leads to another customer.
- Example
- Even if a report screen had a bug in its filter, your Kestrel Ads leads still could not appear in another customer's workspace, because the database filters every row by workspace.
Granular Permissions
25 separate switches, so nobody sees offer prices by accident.
- What it does
- A media buyer needs to see lead flow, but not what each network pays. Alion has 25 independent permissions, all denied by default, so access matches the job, not a role template.
- Why it exists
- Because fixed roles always give someone more than they need, and prices are the first thing to leak.
- Example
- You give your media buyer access to leads, rules and lead journeys but not to offer prices, so the lead and FTD prices of Offer A stay hidden.
PII Field Masking
Your team works without ever seeing customer phone numbers or emails.
- What it does
- Team members and contractors need to do their jobs without seeing customer personal data (PII). Phone, email, IP and network contact details are masked separately for each user, and owners always see the real data.
- Why it exists
- Without it, every person with access to leads can copy a full customer list.
- Example
- A contractor checking failed deliveries to Velora Partners sees each lead's email and phone masked, while the owner of the workspace sees them in full.
Multi-Workspace Accounts
One login, several operations, a different role in each.
- What it does
- Agencies and consultants work across several operations and do not want to juggle logins. One account can belong to several workspaces, with its own role in each.
- Why it exists
- Without it, people share logins or create duplicate accounts, and you lose track of who did what.
- Example
- A consultant is admin in one client's workspace and has read only reporting access in another, all with one login.
Plan-Aware Rate Limiting
Someone else's traffic spike never slows you down.
- What it does
- A traffic burst or a misconfigured lander should never slow the platform down for anyone else. Rate limits follow each workspace's plan and are counted per workspace, not per IP.
- Why it exists
- Because limits counted per IP either block real traffic behind shared IPs or let one noisy account slow down everyone.
- Example
- Another customer's broken lander floods Alion with requests. Their workspace hits its limit, and your leads from Meta keep arriving at normal speed.
Landing Page Access Control
Only your own landers can submit leads to your account.
- What it does
- Only your landers should be able to submit leads to your workspace. The public intake endpoint is locked to a landing page identifier, with an optional allowlist of server IPs.
- Why it exists
- Without it, anyone who finds your endpoint can push fake leads into your rules and onto your networks.
- Example
- A copied form posts to your endpoint without your landing page identifier and is refused. With the IP allowlist on, only your two servers can submit leads at all.
Google and Email Sign-In
Sign in with Google, or with email and properly hashed passwords.
- What it does
- Another platform with another password is how credentials get reused and, sooner or later, leaked. Sign in with the Google account you already trust, or use email with hashing strong enough that a database breach does not hand out working passwords.
- Why it exists
- Because weak password storage turns any breach into stolen accounts.
- Example
- Your team lead signs in with the company Google account. A contractor signs in with email, and Alion stores the password only as a strong hash.
Free Plan with Every Feature
Every feature, 100 leads a month, no card needed.
- What it does
- You should not have to pay to find out whether a system fits how your leads really move. The Free plan has the whole platform with 100 leads a month and 2 users, and paid plans only add lead volume and seats.
- Why it exists
- Because features locked behind a paywall hide whether the tool works for you, and asking for a card first scares people off.
- Example
- You sign up, connect Kestrel Ads and Velora Partners, and route your first 100 leads of the month with every feature on. When volume grows, you move to Team.
Card and Crypto Payment
Pay by card through Stripe, or in crypto through Coinbase Commerce.
- What it does
- A large part of this industry does not or cannot pay by card. Stripe handles cards, with instant prorated upgrades, and Coinbase Commerce handles crypto.
- Why it exists
- Without it, teams that work in crypto simply cannot subscribe.
- Example
- You upgrade mid month by card and pay only the prorated difference. A partner team pays its plan in crypto through Coinbase Commerce.
Hard Limits, Never Surprise Charges
Hit a limit and it stops. You are never billed for overage.
- What it does
- Nobody wants to discover a usage bill after a traffic spike. Reaching a plan limit blocks further use and prompts an upgrade, and nothing is ever billed as overage.
- Why it exists
- Because with usage billing, one bad day of traffic can cost more than the whole month's plan.
- Example
- A Taboola spike takes you to your plan limit on the 20th. Alion stops at the limit and asks you to upgrade, and your bill stays exactly the plan price.
