OX App Suite Storage Plans: How Much You Really Need

How Storage Works Inside OX App Suite Email

Storage inside OX App Suite is not a single number; it is a set of separate allocations that behave differently depending on where the data physically resides. A plan advertised as “50GB” typically splits that capacity across mailbox content, calendar and contact data, and a document layer that operates independently of the inbox itself.

Mailbox Quotas and What Counts Against Them

A mailbox quota in OX App Suite includes message bodies, headers, and any attachments that have not been offloaded elsewhere. Calendar entries, contact records, and task items also draw from the same quota pool in most reseller-provisioned configurations, which surprises administrators who assume the quota applies only to email messages. Once a mailbox approaches its ceiling, inbound delivery can be deferred or bounced entirely, depending on how the mail transfer agent is configured at the domain level.

Deleted items sitting in a trash folder still count against quota until that folder is purged, either manually or on a retention schedule set by the administrator. This trips up new users migrating from consumer webmail services, where trash is often excluded from quota calculations by default. A mailbox that appears full at 95% usage frequently has 10 or 15% of that consumed by trash and junk folders that nobody has emptied in months, which is worth checking before assuming an upgrade is required.

OX Drive as a Separate Storage Layer

OX Drive is provisioned as a distinct storage pool separate from the mailbox itself, closer in function to a synced file storage service than to an email attachment archive. Files uploaded to Drive, shared via link, or edited collaboratively through the suite’s document tools consume this separate allocation rather than mailbox quota, which is why two users with identical mailbox usage can show very different total storage consumption. Drive also retains prior file versions depending on the versioning policy configured for the domain.

This separation matters for planning because a team that emails large attachments back and forth quickly consumes mailbox storage, while a team that stores and links files through Drive instead consumes a different pool at a different rate. Administrators sizing a plan should ask a reseller whether Drive and mailbox allocations are reported separately or combined into one dashboard figure, since the two behave differently under load and fill up for different reasons.

Storage Plan Tiers Available Through Reseller Partners

Reseller-provisioned OX App Suite plans are typically organized into tiers that bundle a mailbox quota, a Drive allocation, and a mailbox count per domain. Exact capacity figures and inclusions vary by reseller and by the specific licensing agreement in place, so the ranges below describe common patterns rather than fixed specifications.

Typical Tier Structures and Capacity Ranges

Entry-level tiers commonly bundle 10GB to 25GB per mailbox, aimed at solo professionals and very small teams that primarily send text-based correspondence with occasional attachments. Mid-tier plans typically move into the 25GB to 50GB range per mailbox and often introduce a separate, larger Drive allocation intended for document collaboration rather than pure email storage. Enterprise-oriented tiers frequently offer 50GB or more per mailbox, sometimes with the option to pool unused capacity across the domain rather than fixing it per user.

Introductory Pricing vs. Renewal Terms

Introductory pricing on hosted email plans commonly reflects a discounted first term, with renewal pricing reverting to a higher published rate, a pattern common across the hosted-email market rather than something unique to any single reseller. Storage inclusions can also shift at renewal if a reseller adjusts its licensing tier, so a plan that included 30GB at signup is not guaranteed to include the same amount indefinitely without written confirmation. Buyers comparing quotes should ask specifically whether the quoted storage figure is locked for the contract term or subject to change at renewal.

Grace periods for storage overages, the window between hitting a quota ceiling and losing send or receive functionality, also vary by reseller agreement and are not standardized across the industry. Renewal reviews often reveal a plan in which the mailbox count grew organically over the course of a year. However, no one revisited whether the original storage tier still matched actual usage, resulting in avoidable overage fees. Locking both the storage figure and the overage policy into a written quote before signing avoids most of this ambiguity later.

Mailbox Storage vs. OX Drive Storage

Mailbox storage and Drive storage answer different questions; one measures how much correspondence and calendar data a user has accumulated, the other measures how much shared and collaborative content a team has produced. Conflating the two when sizing a plan is the most common estimation error administrators make.

What Lives in the Mailbox

Message threads, including every reply and forward in a chain, accumulate inside the mailbox quota even when the substantive new content in each message is minimal. Calendar events with recurring patterns spanning years, along with contact records synced from mobile devices, also live in this same pool, meaning a mailbox can fill up from metadata accumulation rather than from large file attachments alone. Shared address books provisioned at the domain level typically draw on a separate administrative allocation rather than on individual mailbox quotas. However, this varies depending on how the domain was originally configured.

Junk and spam folders that are not actively managed by a filtering policy also consume mailbox quota. Because spam volume is often higher than legitimate mail volume for a public-facing address, this folder can become a larger contributor to quota consumption than most administrators expect. Setting an automatic purge policy for junk folders, typically a 30-day rolling window, frees up meaningful space without risking legitimate correspondence, since flagged spam rarely needs retention beyond a short review window.

What Lives in Drive and Documents

Files created or edited through the suite’s built-in document editor are stored natively in Drive format, and collaborative editing sessions generate incremental version history that also counts against the Drive allocation unless version retention is capped by policy. Shared folders used for cross-team collaboration draw from the same pool, so a marketing team storing brand assets and a finance team storing spreadsheets both compete for the same Drive quota when they share the same domain-level allocation.

Large media files, video assets, high-resolution design files, and archived project folders are the most common cause of Drive quota exhaustion, far more often than day-to-day document editing. Teams that treat Drive as a general-purpose file server rather than a working-document space tend to hit ceilings faster than teams that use it primarily for active collaboration and archive completed projects to external cold storage instead. Reviewing Drive usage by folder size at least quarterly catches this pattern before it forces an unplanned upgrade.

Estimating Storage Needs by Business Size

Storage requirements scale with team size, but not in a straight line; usage patterns shift meaningfully as an organization moves from a single user to a multi-department team, which is why a flat per-seat estimate often underprices or overprices the actual need.

Solo Consultants and Small Teams

A solo consultant or freelancer handling text correspondence, invoices, and occasional PDF attachments typically stays comfortably within a 10GB to 15GB mailbox allocation for several years before approaching a ceiling. The main variable is attachment habit: a consultant who emails signed contracts and scanned documents accumulates storage faster than one who relies on e-signature platforms and shares links instead of file copies. Small teams of two to five people generally follow the same pattern individually. Still, they should account for shared calendar and contact data, drawing from a pooled allocation if the domain is configured that way.

Teams at this scale rarely need a dedicated Drive allocation beyond what is included in a basic or standard tier, since collaborative document work is usually light and file sharing tends to occur via direct attachments rather than persistent shared folders. The more common storage pressure point for small teams is calendar and contact accumulation over multiple years of continuous use, rather than any single large attachment. It is worth flagging this to a reseller when requesting a quote, so the plan isn’t oversized for mailbox capacity while undersized for longevity.

Agencies and Growing SMBs / Enterprise

Agencies and growing SMBs typically need both a larger mailbox allocation and a meaningfully larger Drive pool, since client work generates recurring file exchange, design proofs, contracts, and deliverables, on top of standard correspondence volume. A ten-person agency handling client creative assets can exhaust a 25GB Drive allocation within a year if project archives aren’t moved to cold storage after handoff, even if individual mailboxes stay well under quota. Department-level usage also varies widely within the same organization: sales and account management mailboxes tend to accumulate faster than internal operations mailboxes, even when handling similar volumes of correspondence.

Enterprise organizations generally benefit from pooled or negotiated storage arrangements rather than fixed per-mailbox tiers, since usage across dozens or hundreds of mailboxes rarely distributes evenly and a pooled model absorbs that variance without forcing individual upgrades. Compliance-driven retention requirements, common in regulated industries, also push enterprise storage needs meaningfully higher than raw usage would otherwise suggest, since retained mail and archived records must remain accessible for audit purposes well beyond the point at which a user would otherwise have deleted them.

Attachment Behavior and Its Impact on Mailbox Storage

Attachments are the single largest variable in mailbox storage consumption, and how they’re stored, not just how many are sent, determines how quickly a quota fills.

How Attachments Are Stored and Counted

Every recipient copy of a message with an attachment stores that attachment independently within their own mailbox quota, meaning a single 5MB file sent to ten internal recipients consumes roughly 50MB of aggregate mailbox storage across the domain rather than 5MB shared once. This per-recipient duplication is standard behavior across nearly all IMAP-based mail systems, not a quirk specific to any one provider. Still, it catches administrators off guard when they estimate storage based on files sent rather than files stored. Forwarded messages compound this further, since each forward typically re-attaches the original file rather than referencing it.

Encoding overhead adds a further, smaller cost: attachments transmitted via SMTP are base64-encoded for transport, which increases the effective stored size of a file by roughly a third compared to its original file size on disk. A 10MB PDF therefore consumes closer to 13MB or 14MB of mailbox quota once stored, a detail that matters when a team is estimating storage needs based on the raw file sizes they see in a folder rather than the encoded size that actually lands in the mailbox.

Encrypted Attachments and OX Guard

OX Guard, the suite’s built-in encryption component, adds a layer to attachment storage math because encrypted messages and their attachments are stored in an encrypted container rather than as plain MIME content, which typically increases the storage footprint compared to an unencrypted equivalent. Organizations handling sensitive client data, contracts, financial records, and health-adjacent information often enable OX Guard selectively for specific correspondence rather than domain-wide, both to manage this storage overhead and because encrypted messages require the recipient to have compatible key handling in place.

Teams evaluating whether to enable OX Guard broadly should factor in that encrypted attachment storage isn’t just marginally larger; for high-volume attachment users, the cumulative effect across a year of correspondence can meaningfully shift when a mailbox approaches its quota ceiling compared to unencrypted use. A reasonable middle ground many agencies land on is enabling encryption for a defined set of sensitive correspondence use cases while leaving routine internal mail unencrypted, which keeps storage growth predictable while still meeting the security requirements for sensitive exchanges.

Get a Plan Sized to How Your Team Actually Sends Attachments

Attachment habits, encryption needs, and per-recipient storage duplication are the details a generic storage estimate misses, and they’re exactly what a proper sizing conversation should account for before you commit to a tier. As an Authorized Partner and reseller of OX App Suite Email Service, Hiya Digital can review your actual sending patterns and match a plan to them rather than guessing.

Get a Storage Sizing Consultation →

Shared Storage Pools vs. Per-Mailbox Allocation

Reseller-provisioned domains generally offer two structural approaches to distributing storage across a team: a fixed per-mailbox limit that each user can’t exceed regardless of what others on the domain are using, or a pooled model where total domain capacity is shared and redistributed based on need.

How Pooled Storage Is Distributed

In a pooled configuration, the domain administrator typically sets a total capacity and either allows storage to be drawn down organically as users consume it or applies soft per-user caps within the shared pool to prevent any single mailbox from consuming a disproportionate share. This model suits organizations with uneven usage across roles, a sales team generating heavy attachment traffic alongside an operations team with minimal storage needs, since capacity flows to where it’s actually used rather than sitting unused in lightly-loaded mailboxes.

The trade-off is visibility: pooled storage requires more active monitoring by an administrator, since a handful of heavy users can quietly consume the majority of the domain’s capacity, leaving less headroom than the average-per-user figure would suggest. Most reseller dashboards provide per-mailbox usage breakdowns even under a pooled model, which administrators should check periodically rather than relying on the aggregate figure alone to judge whether the domain is approaching capacity.

When Fixed Per-Mailbox Limits Make More Sense

Fixed per-mailbox allocation works better for organizations that want predictable per-user cost and behavior, particularly where mailboxes are billed or charged back to individual departments and a shared pool would complicate that accounting. It also limits the risk of one compromised or misconfigured mailbox, for example, one caught in a mail loop or receiving a large volume of unsolicited attachments, from consuming capacity that affects the rest of the domain’s users.

The practical downside is that fixed limits require more frequent individual upgrades as specific users outgrow their allocation, even while the domain overall has unused capacity sitting in other mailboxes. Organizations with highly variable role-based usage, where a handful of users genuinely need much more storage than the rest of the team, often find fixed limits create more manual administrative overhead over time than a pooled model would. However, the tradeoff in predictability is a legitimate reason some administrators prefer it anyway.

OX App Suite Storage vs. Google Workspace and Microsoft 365

Storage comparisons across major business email platforms are frequently framed around headline mailbox figures alone, which misses meaningful differences in how each platform structures and pools that storage in practice.

Comparing Baseline Allocations

Google Workspace’s lower business tiers typically pool storage across Gmail, Drive, and Photos into a single combined allocation per user, while Microsoft 365’s business tiers generally separate Exchange mailbox storage from OneDrive storage as two distinct quotas. OX App Suite’s reseller-provisioned model most closely resembles the Microsoft approach in that mailbox and Drive storage are tracked separately. However, exact figures depend entirely on the specific tier a reseller has provisioned rather than a single standardized number across the platform.

Sync Behavior Differences That Affect Perceived Storage

OX App Suite relies on CalDAV and CardDAV as its standard synchronization layer for calendar and contact data across third-party clients; these are open, widely supported standards rather than proprietary sync protocols. This matters for perceived storage indirectly because CalDAV/CardDAV sync is stateless and pulls current data rather than maintaining a separate cached copy per device, as some proprietary sync layers do; users typically don’t see the same kind of duplicated local storage bloat across multiple synced devices.

Google and Microsoft both support open calendar and contact standards to varying degrees, but generally push users toward their own native sync mechanisms first, which can create device-side storage duplication unrelated to server-side mailbox quotas yet still affect a user’s perception of “storage” on their phone or laptop. Administrators evaluating platforms purely on server-side quota numbers should account for this distinction, since a platform with a smaller headline mailbox figure but leaner sync behavior can still deliver a better practical storage experience for end users than a platform with a larger quota and heavier client-side caching.

Storage Growth, Archiving, and Migration Considerations

Storage needs rarely stay flat; a mailbox sized correctly at onboarding typically needs revisiting within eighteen to twenty-four months as correspondence, calendar history, and Drive content accumulate.

Archiving Strategies Before You Hit the Ceiling

Archiving mail older than a defined threshold, commonly 12 to 24 months, into a separate, lower-cost storage tier or a local archive file is the most effective way to extend the usable life of an existing plan without upgrading. Most reseller-provisioned OX App Suite configurations support this through IMAP-based archive folders that keep older mail searchable while moving it out of the primary quota calculation, though the exact mechanism and whether it reduces quota consumption depend on how the reseller has configured archiving at the domain level.

Grace periods for storage overages, the window between hitting a quota ceiling and losing mail functionality, vary by reseller agreement, so confirming this specific policy in writing before it becomes relevant avoids a surprise service interruption. A practical approach many administrators use is setting an internal alert at 80% of quota rather than waiting for the platform’s own warning threshold, since that buffer provides time to archive or request an upgrade before any functionality is affected.

Migration Scenarios That Change Storage Math

Migrating an existing mailbox into OX App Suite from another platform often imports more historical data than a fresh mailbox would organically accumulate, since years of prior correspondence, calendar entries, and contacts transfer in a single batch rather than building up gradually. Administrators planning a migration should request a pre-migration storage estimate based on the source platform’s reported usage rather than assuming the destination mailbox quota matches typical fresh-account sizing, since a mailbox migrating in at 40GB of existing data needs a tier sized well above that figure from day one.

Selective migration, importing recent mail and calendar data while leaving older archives on the source platform or in a separate export file, is a common way to control this, particularly for organizations migrating primarily to reduce cost or improve collaboration features rather than to preserve every historical record inside the live mailbox. This approach also shortens migration time and reduces the risk of hitting a new mailbox’s quota ceiling on the very first day of use, which is a more common problem during migrations than most administrators anticipate.

Security, Encryption, and Their Effect on Storage Planning

Security features and storage capacity interact more directly than most buyers expect, since several of the protections that matter most for business email add measurable overhead to how much space correspondence actually consumes.

OX Guard Encryption Overhead

Beyond the per-message overhead already relevant to attachment-heavy correspondence, OX Guard’s encryption model also affects how key material and encrypted message metadata are stored, as each encrypted thread maintains its own key-handling data alongside the message content. For organizations that enable encryption across a large share of their correspondence rather than selectively, this cumulative overhead is worth factoring into the storage tier chosen at signup, rather than discovering it as an unplanned driver of an early upgrade.

The practical guidance most administrators land on is treating OX Guard as a targeted tool for specific sensitive workflows, client contracts, financial exchanges, anything with genuine confidentiality requirements, rather than a blanket default, which keeps both storage growth and key-management overhead proportional to actual risk rather than applying encryption uniformly across low-sensitivity internal chatter that doesn’t need it.

Compliance-Driven Retention and Its Storage Cost

Regulated organizations, those subject to data protection frameworks such as the General Data Protection Regulation or industry-specific retention rules, often need to retain mail well beyond the point at which a user would naturally delete it. That retained volume draws against storage capacity regardless of whether it’s actively used. This creates a structural tension between minimizing storage cost and meeting a retention obligation that legally can’t be shortened, which is why compliance-heavy organizations typically need an archive add-on or a dedicated retention tier rather than trying to fit years of retained correspondence inside a standard mailbox quota.

Providers pursuing recognized security and compliance frameworks, such as SOC 2 or ISO/IEC 27001, typically document specific data handling and retention practices as part of the certification process. Organizations with compliance obligations should confirm which certifications apply to the specific infrastructure on which their reseller-provisioned mailbox runs, since certification scopes vary and shouldn’t be assumed from a general provider claim alone.

Signs You’ve Outgrown Your Current Storage Plan

Most storage upgrades happen reactively, after a bounced message or a blocked upload, rather than proactively based on a usage trend, and both technical and business signals typically appear well before that point if anyone is watching for them.

Technical Warning Signs

Recurring quota warning notifications, even those dismissed rather than acted on, are the clearest early indicator that a mailbox is trending toward its ceiling faster than the plan anticipated. Delayed or bounced inbound mail during peak usage periods, often around end-of-month invoicing or seasonal correspondence spikes, signals that a mailbox is intermittently hitting its limit even if it shows headroom on an average day, which average-usage dashboards can mask entirely.

Slower search and folder-loading performance in webmail, particularly in mailboxes that have accumulated years of unpurged trash and junk folders, is a secondary but common technical sign worth checking before assuming an upgrade is the only fix, since a cleanup pass sometimes resolves the immediate pressure without any plan changes at all. Drive upload failures or sync errors on shared folders point to the separate Drive allocation approaching its own ceiling, which requires a different remedy than a mailbox quota increase and warrants separate diagnosis rather than assuming both pools are equally full.

Business Warning Signs

Headcount growth is the most obvious business trigger. Still, the more commonly missed signal is a shift in how the team works rather than how many people are on it. A team that starts sharing more design files, video assets, or large proposal documents through Drive will outgrow a plan sized for its headcount well before a plan sized for its actual collaboration volume would need to be revisited. Client-facing teams handling growing attachment volume, particularly agencies and consultancies taking on larger accounts, often hit this pattern within a year of a plan being sized correctly at onboarding.

A useful discipline is to review actual per-mailbox and Drive usage against the provisioned tier at each renewal cycle, rather than only when a problem surfaces, since a gradual trend toward the ceiling is far easier to address with a planned upgrade than a sudden capacity crisis is to fix under pressure. Organizations that tie this review to their annual renewal conversation with their reseller generally avoid both the overage risk and the cost of over-provisioning a plan that far exceeds current usage.

Frequently Asked Questions

Does unused OX Drive storage roll over or convert into extra mailbox quota?

No, mailbox quota and Drive quota are tracked as separate pools in most reseller-provisioned configurations, so unused Drive capacity doesn’t automatically offset a mailbox that’s approaching its ceiling, and vice versa. If your team consistently uses far less Drive storage than mailbox storage, it’s worth asking your reseller whether a custom allocation split is available rather than accepting the default ratio bundled into a standard tier. Some reseller agreements allow this kind of rebalancing at renewal even when it isn’t offered mid-contract, so the right time to raise it is usually during a plan review rather than immediately after noticing the imbalance.

What specifically should I ask my reseller before signing a storage plan?

Beyond the headline capacity figure, ask whether the quoted storage is locked for the full contract term or subject to change at renewal, what the overage grace period is in writing, whether mailbox and Drive allocations are pooled or fixed per user, and whether archived mail counts against active quota. Also confirm whether the quote reflects introductory or renewal pricing, since storage inclusions sometimes shift between the two even when the dollar price looks similar. Getting these specifics in writing before signing avoids the most common source of disputes later: a mismatch between what was verbally described during sales conversations and what the service agreement actually specifies.

How does migrating from Microsoft 365 or Google Workspace affect the storage tier I need?

A migration typically imports your entire mailbox history in a single batch, so the tier you need is based on your source platform’s current usage, not a fresh-account estimate. If your Microsoft 365 or Google Workspace mailbox currently shows 35GB of usage, a 25GB OX App Suite tier won’t accommodate a full migration without either selective import or an immediate upgrade. Requesting a usage export from your current platform before getting a quote gives your reseller an accurate baseline, and selective migration, importing only the last twelve to twenty-four months, is a common way to fit within a smaller tier if you don’t need the full historical archive live in the new mailbox.

Is OX App Suite storage compatible with Outlook, or only the native webmail client?

OX App Suite supports Outlook connectivity, typically through IMAP/SMTP configuration or a dedicated connector, depending on how the reseller has provisioned the domain. Mail, calendar, and contacts sync through that connection, much as they would with any standards-based mail platform. Storage quota is enforced server-side regardless of which client you use to access the mailbox, so switching between Outlook and OX App Suite’s native webmail doesn’t change how much quota is consumed; it only changes how the data is displayed and cached locally. Local Outlook caching (an OST or PST file) does consume storage on the device itself, separate from server-side mailbox quota, which is worth noting if a user’s local machine is running low on disk space even though their server-side mailbox shows headroom.

Do mobile apps consume storage differently than desktop or webmail access?

Mobile apps typically sync a rolling window of recent mail rather than caching the full mailbox locally, which reduces on-device storage compared to a desktop client but doesn’t change server-side quota consumption at all; quota is calculated the same way regardless of access method. Push notification behavior on mobile can also trigger more frequent partial syncs than a desktop client checking on a fixed interval, which affects data usage and battery more than storage. Users switching between the native OX App Suite mobile app and a third-party mail app configured via IMAP may notice different local caching behavior. Still, neither affects the actual quota figure an administrator sees on the backend.

How do I confirm my storage plan’s grace period in writing before I rely on it?

Ask your reseller directly for the exact number of days or a percentage-based grace window between hitting quota and losing send/receive functionality, and request that figure in the service agreement or in a written quote rather than accepting a verbal description during a sales call. Grace periods are not standardized across resellers or platforms, so a figure quoted for one plan tier may not automatically apply to another tier or to a custom enterprise arrangement. If the written agreement doesn’t specify a grace period, treat it as a gap to clarify before signing rather than assuming a default industry-standard window applies.

What happens to email that arrives after a mailbox hits its storage ceiling?

Behavior varies by configuration, but the most common outcome is that inbound mail is deferred by the sending server and retried for a limited window, typically several days, before bouncing back to the sender as undeliverable, since a full mailbox generally can’t accept new messages regardless of the sending server’s retry attempts. Outbound mail is also frequently blocked once a mailbox is full, meaning a user can be locked out of sending replies, even to messages already in their inbox. This is a strong argument for setting an internal usage alert well before reaching 100% of quota, since the consequence isn’t a warning banner; it’s a functional mail outage for that specific mailbox.

Does OX Guard encryption apply per message, or does it need to be enabled for the entire mailbox?

OX Guard is generally applied selectively, per message or per correspondence thread, rather than as an all-or-nothing mailbox-wide setting, which lets a user encrypt a specific sensitive exchange without adding encryption overhead to routine internal correspondence. This selective approach is also why most administrators recommend using it for defined sensitive-data workflows rather than defaulting to encrypting everything, since the storage and key-management overhead scales with the amount of correspondence encrypted, not being a fixed cost regardless of usage. Recipients need compatible key handling to open encrypted messages, so internal-only threads between users on the same OX Guard-enabled domain tend to work more smoothly than encrypted exchanges with external recipients on unrelated platforms.

Can I get a custom domain email address on any storage tier, or only higher tiers?

Custom domain support is generally available across OX App Suite tiers provisioned by resellers, including entry-level plans, since domain configuration is largely independent of the storage capacity bundled into a given tier. What does vary by tier is often the number of mailboxes included under that domain and whether features like domain-wide shared calendars or pooled storage are available, so it’s worth confirming domain and mailbox-count inclusions separately from the storage figure when comparing quotes. DNS configuration for the custom domain, MX, SPF, and DKIM records pointed to the provider’s mail infrastructure is typically the same process regardless of the storage tier selected.

Is a smaller OX App Suite storage plan actually suitable for a business, or is it built for personal use?

Entry-level OX App Suite tiers are built and licensed for business use, including custom domain support and administrative controls, rather than being scaled-down personal email products; the smaller capacity reflects lighter expected usage, not a different product category. A solo consultant or a two-person team with modest attachment habits is a legitimate long-term fit for an entry-level tier, rather than something to outgrow quickly by default, provided actual usage is reviewed periodically rather than assumed to remain static as the business grows. The distinguishing factor for business suitability is less about the storage figure itself and more about whether the plan includes the administrative, security, and domain features a business needs, regardless of mailbox size.

Glossary

MX Record: A DNS entry that specifies which mail server is responsible for accepting email on behalf of a domain.

SPF (Sender Policy Framework): A DNS TXT record listing which servers are authorized to send mail for a domain, used to reduce spoofing.

DKIM (DomainKeys Identified Mail): A cryptographic signing method that lets a receiving server verify a message wasn’t altered in transit and genuinely originated from the claimed domain.

DMARC: A policy layer built on SPF and DKIM that tells receiving servers what to do with messages that fail authentication checks.

IMAP / POP3: Protocols used to retrieve mail from a server; IMAP keeps mail synced across devices, while POP3 typically downloads and removes it from the server.

SMTP: The protocol used to send and relay email between servers.

TLS: Transport Layer Security, used to encrypt the connection between mail servers or between a client and server during transmission.

CalDAV / CardDAV: Open standards used to sync calendar and contact data, respectively, across different mail clients and devices.

OX Guard: OX App Suite’s built-in encryption component for securing individual messages and attachments.

OX Drive: OX App Suite’s file storage and collaboration layer, tracked separately from mailbox quota.

OX Documents: The suite’s native document editing and co-editing tool, integrated with OX Drive storage.

Mailbox Quota: The storage limit assigned to an individual mailbox, covering messages, calendar, contacts, and unarchived attachments.

Storage Pooling: A model where total domain storage capacity is shared across mailboxes rather than fixed per user.

Archiving: Moving older mail out of active mailbox quota into a separate, searchable storage tier.