Every question, one page.

No. Boita is for anyone who moves a lot of data and has hit the bottleneck: labs sending sequencing runs, hospitals moving imaging studies, engineering teams exchanging CAD and BIM models, satellite and drone operators, ML teams moving datasets, IT teams doing off-site copies, game studios shipping builds, print houses receiving artwork — and yes, studios delivering renders and episodes. The engine, the links, the portals and the automation are the same; only the examples change.

Ordinary uploads run over TCP, which slows down every time a packet is lost and never recovers the distance to a far-away server. Boita moves data with an accelerated transfer engine over UDP with its own rate control, so a transfer climbs to your line rate and stays there whether the other end is across town or across an ocean. Big jobs also run as several parallel sessions: 45 Mbps per session, 10 sessions on Pro (450 Mbps), 50 on Scale (2.25 Gbps), 100 or more on Enterprise.

Not to start. The web app uploads and downloads in the browser, and recipients and portal uploaders need nothing installed either. For full speed, resume and watch folders, install the free desktop app (macOS, Windows, Linux) or the headless agent on a server; both carry the transfer engine, so there is no second client to keep updated.

In the desktop app, it resumes on its own at the exact byte when the connection, the computer or the app comes back; completed files are never re-sent. From a browser or the phone app, an interrupted transfer starts again (files that already finished stay finished), so use the desktop app for large files.

Boita uses whatever line you have; the plan sets the ceiling, not the floor. If your network blocks UDP, transfers fall back to an HTTPS path automatically and the app says which path you are on. On a 2G or 3G connection the delivery, portal and Files pages offer a low-bandwidth mode that switches off previews, covers and animations so the page and the link still work.

No. Recipients open a share page, see the files and download in the browser with nothing to install. The page offers the free desktop app for full speed and resume on very large deliveries.

No. Plans are flat monthly amounts, billed in your local currency (INR in India). We do not charge per GB downloaded, and re-downloads are free. If storage overage ever applies it is shown before it happens, never after.

In India: files, the transfer server, the application and the database run in Google Cloud, Mumbai, with encrypted backups in Mumbai and Singapore. The Trust page lists every location and sub-processor. Regional nodes elsewhere are available on request for Enterprise; a self-managed node in your own AWS account is also possible with our Terraform module.

Yes — Boita for iPhone and Android: your dashboard, files and search, share links with receipts, upload portals, review and approval, transfers, automations, members and security. "Send from my computer" lets you pick files on your Mac or PC from the phone and have the desktop app send them on the fast path. Uploads straight from the phone go over HTTPS at standard speed.

Free is ₹0 with 10 GB. Pro is ₹499 a month with 1 TB, Scale ₹7,999 a month with 10 TB, Enterprise is custom. Visitors outside India see the same plans in USD, EUR, GBP, AED, SGD or AUD. No per-GB fees, no download charges, GST invoices in India. Sign up free at app.boita.io; teams moving terabytes a month can ask for a guided pilot.

No. Every plan is a flat monthly amount in your currency. Downloads and re-downloads are free, and there are no per-GB transfer fees. If storage overage ever applies it is shown before it happens.

Plans are built for real production workloads, not for reselling bandwidth. Lower plans carry a monthly transfer allowance; if you are consistently far above it we will talk to you about the right plan before anything is limited.

Each plan sets a ceiling per transfer: a rate per session times the number of parallel sessions. Free runs 2 sessions at up to 10 Mbps each (20 Mbps), Pro 10 sessions at up to 45 Mbps each (450 Mbps), Scale 50 sessions (2.25 Gbps), Enterprise 100 or more (4.5 Gbps and above). Your own line is the other limit: a plan never makes a 100 Mbps connection faster than 100 Mbps, but unlike ordinary uploads it lets you use all of it regardless of distance. You can lower the rate from the app during a transfer; you cannot raise it above the plan.

No. Recipients download from a share page and clients upload through a portal without an account or a plan of their own.

Yes. Cancel from your workspace settings; your plan runs to the end of the billing period and your files follow the published retention policy after that.

In India, subscriptions are billed in INR with GST invoices and a GSTIN field. Elsewhere, we issue tax invoices in your local currency: USD, EUR, GBP, AED, SGD or AUD, chosen from your region and changeable on the pricing page.

Every INR charge comes with a GST tax invoice in the company format, with your GSTIN on it, and refunds come with a credit note. UPI Autopay, cards and one-off monthly payments are live: you pay from inside the workspace and the plan changes immediately.

Pro and Scale can be billed monthly or annually. A year costs ten months of the monthly price, so two months are free — about 17% off: Pro ₹4,990 a year instead of ₹5,988, Scale ₹79,990 instead of ₹95,988, and the same in every other currency. GST is added on top for INR either way. You can switch from the workspace: monthly to annual takes effect at once, annual back to monthly when the year you have paid for ends. Free has no annual plan and Enterprise is quoted.

Monthly plans can be cancelled at any time and run to the end of the period, with no refund for the remainder. An annual plan can be refunded pro rata within 14 days of the purchase or renewal date, from the workspace’s billing settings: the months you have used are charged at the monthly price of your plan and the rest of what you paid comes back, counting the month already under way as used, and the workspace goes back to Free. Usage-based overage, where it applies, is not refundable. The full policy is at /legal/refunds.

Boita is built and operated by Aariko Systems, a small team in Pune, India. The company grew out of the founder's earlier 3D rendering business, where deliveries of 10 to 20 TB per job were normal and the transfer was the bottleneck.

Neither, on purpose. It has the ease of a consumer sharing link (recipients need no account and nothing to install) and the mechanics of an enterprise transfer suite (UDP acceleration, parallel sessions, resume in the desktop app, checksums, watch folders, an agent and a CLI), on flat plans without per-seat or per-GB pricing.

An optional cold tier, available on request when it ships: aged deliveries can be moved out of hot storage to an archive with proof-of-storage, on decentralised storage or on a domestic object store for India-residency workspaces, and restored on demand with the restore time shown. It is only ever an archive; transfers never touch it. The archive tier that ships today (Scale and above) moves folders to cold storage with a manifest and restores on demand.

Partly. Enterprise workspaces can auto-deliver anything landing in a folder to their own transfer server or S3-compatible object storage, and can stand up a self-managed transfer node in their own AWS account with our Terraform module. The web app, accounts and receipts stay with us.

Yes. The desktop app ships as an AppImage, and the headless boita-agent with the boita CLI runs on servers, NAS boxes, lab instruments and render nodes under systemd. The web app works in any modern browser.

Yes. Pro and above get scoped API keys for the same REST surface the apps use (files, share links, portals, transfers, receipts), signed webhooks, an OpenAPI description with TypeScript and Python SDKs, and REST hooks for Zapier, Make and n8n. See boita.io/developers.

English, everywhere: the app, the delivery and portal pages, the emails and this site. Other languages are not offered for now.

Write to hello@boita.io for anything commercial, open a ticket from Support inside the app (or support@boita.io) once you are a customer, and security@boita.io for vulnerability reports. Every plan has a promised first-reply time; Scale adds live chat, Enterprise adds scheduled calls and a named contact. A person replies.

No. They open their personal link from the invitation (or verify their email with a code) and everything they do is attributed to them on the receipt. Nothing to install.

No. The player, the image viewer and the PDF viewer all work from proxies rendered on our servers. Downloads are separate and can be switched off with a view-only link.

No. PDFs (proofs, drawings, reports), stills, exported CAD views and layered artwork, imaging exports and audio get the same notes, drawings and approvals; video adds the frame-accurate player. Anything else is approved from its row without a viewer.

Decisions are per version. A replaced file goes back to Pending review, the previous decision stays on the previous version, and version compare shows both.

It can only do what you wrote, and you can see that before it runs: Test shows each action against the last real event with nothing sent. A share-link action also respects workspace policy — if links must have a password, the rule fails cleanly instead of sending an open link.

No. Rules are built in the app from dropdowns and templates. If you do have developers, the same events are available as signed webhooks, a polling event stream and REST hooks for workflow platforms.

Rules are kept. On a plan without automations they stop firing until the plan includes them again; nothing is deleted.

Only the attachments are kept, under Inbox/<date>/<subject> in your workspace. The sender gets a confirmation or a reason it could not be filed. The panel says so if inbound mail is not switched on for your deployment yet.

A project sits on a folder and groups everything created from the project page: links, portals, auto-delivery rules and transfers into that folder. The files stay ordinary files; removing the project changes nothing about them.

No. Search covers names, paths, tags, custom fields and the technical details probed from media files (codec, resolution, frame rate, audio layout, duration). It does not read documents.

A move copies to the destination, checks the copy against the recorded checksum, and only then removes the source. If anything fails, the source is untouched and the job says which files.

Two ways. Auto-delivery pushes everything that lands to your own S3-compatible bucket or transfer server within minutes. A self-managed transfer node in your AWS account (Terraform module) keeps the storage under your account while Boita runs the workspace, links and receipts.

SOC 2 Type II is in progress on a compliance platform; ISO/IEC 27001 is targeted within 12 to 18 months of launch; the TPN self-assessment against the MPA content-security guidelines is written control by control and available on request with its gap list. Nothing is claimed as certified until it is.

The SIEM stream carries every workspace event; status.boita.io announces incidents and maintenance; every incident gets a written post-mortem. The Trust page lists recovery objectives and the backup schedule.

Yes, published at /legal/dpa with the sub-processor list and the DPDP statement. Counsel review of the pack is in progress; custom terms are handled per contract.

No. Rules can email, tag and create links without any chat app. Slack and Teams add a channel as a destination and let people make a link from chat.

Yes. Choose the drive as the destination when you send, or make it an automation action for a folder; the delivery lands there and the receipt still records it.

Portals for people, the CLI and the agent for machines, links for outbound, and Boita itself as an SFTP endpoint (Pro and above) for instruments and legacy systems that can only speak SFTP.

You can, over HTTPS at standard speed; if it is interrupted, it starts again. For multi-GB deliveries the fast path is Send from my computer: pick the file on your Mac or PC from the phone and the desktop app sends it.

No. Delivery and portal pages open in any mobile browser. The app adds push notifications, QR scanning and a home screen for people who work in Boita every day.

Yes. Sign in with your identity provider on Enterprise, or with a passkey or an authenticator code on any plan.

From the route. A textbook model of TCP throughput given the round-trip time and loss on the path, granted four parallel streams to be fair to multipart uploaders and capped at your line rate. The assumption is printed on the receipt and the same model runs the calculator on the home page.

It is a PDF you send them, branded with your name and logo on Scale and above. It lists every delivery in the period, its files and checksums, and who opened and downloaded what, with the platform named only in the footer.

No. Insights are computed per workspace from your own receipts and transfers, and cached per workspace.

Yes. They tap the link in the WhatsApp message, and any reply in that chat is matched to the delivery and shown to you as a comment. They never need a Boita account.

Yes. Add your GSTIN and billing address under Plan & billing; it is checked for format and state, and every invoice and credit note carries it with CGST + SGST or IGST as applicable.

Files and the database are in Mumbai. Encrypted backup copies are also kept in Singapore for disaster recovery; the sub-processor list on the Trust page says exactly what leaves the country (transactional email, crash reports without file contents).

Yes, within your plan. A big job runs as several parallel sessions; Pro allows more than Free, Scale allows many, and Enterprise is custom. The far end and your own link are the real ceilings.

No. Recipients open a share page and download: in the free Boita desktop app at full speed with resume, or in the browser with nothing to install, slower, where an interrupted download starts again.

It waits. A file is uploaded only after it has stopped changing for a set time, so partial frames never ship.

No. Plans are flat monthly amounts sized by storage, retention and seats. There are no per-GB transfer fees and no charge for downloads or re-downloads.

Yes. The delivery receipt records who downloaded which file and when, with per-file checksums and a CSV verification report; on Scale and above it exports as a PDF for the platform.

Links are not capped by file size; your storage quota is the limit. Scale includes 10 TB and Enterprise is custom.

Yes. Boita falls back to an HTTPS path automatically. It is slower but still encrypted, and the app tells you which path you are on so IT knows what to open.

Yes. Send each supplier an upload portal link. Their upload lands in its own inbox folder in your workspace and both sides get a completion email. From a browser an interrupted upload starts again; the free desktop app resumes.

In the desktop app, the transfer waits and resumes from its checkpoint when the link is back, and nothing already uploaded is sent again. A browser upload starts again.

Yes. A watch folder can send only between chosen hours, and the workspace can cap transfers during office hours; the transfer server enforces the cap. You can also lower the rate from the app during a transfer.

No. Boita moves any file type as is. Images and PDFs get previews; point-cloud viewers are not planned.

Yes. The desktop app ships as an AppImage, and the headless boita-agent runs watch folders on a server under systemd, with the boita CLI for scripts.

Boita publishes a DPDP statement and a data processing summary and stores data in India. It does not claim HIPAA or ISO certification; an independent penetration test and SOC 2 are planned.

Yes. Turn on recipient verification: the recipient confirms their email with a one-time code before the file list is shown, and the receipt names them. Add a password and a download limit as well.

Support works from metadata, and with sender-side encryption nobody at Boita can read the files. Break-glass access to unencrypted contents will require a ticket, a second approver and a time limit, and appear in your audit log; this process is being built.

No. The share page offers the free Boita desktop app for the fast path with resume, and a browser download with nothing to install: slower, and an interrupted download starts again.

Yes. Scoped API keys and signed webhooks (Pro and above), an OpenAPI description with TypeScript and Python SDKs, and the boita CLI that ships with the headless Linux agent.

Share retention is per plan: 3 days on Free, 14 on Pro, 30 on Scale, custom on Enterprise. You get a reminder before a link expires and can extend it with one click.

Yes. Files and the transfer server run in Google Cloud, Mumbai; the trust page lists where everything lives and every sub-processor.

Boita is a transfer and storage workspace. It is a good destination for off-site copies and close-out archives, with checksums, versions and a trash window, but it does not do snapshots, deduplication or bare-metal restore.

Every file shows the checksum the server recorded when it arrived. Compare it with the checksum of your local copy, or use the CSV verification report on a delivery receipt.

A cryptographic proof, produced by a decentralised storage provider, that the data is still being held as agreed. Boita will record it on archived items when that archive backend ships.

Yes. The archive tier is domestic object storage; a decentralised backend is optional and coming.

Yes. They open the share page and download: in the free Boita desktop app at full speed with resume, or in the browser with nothing to install, slower, where an interrupted download starts again.

Revoke the link. Download tokens expire in minutes, so revocation stops new and resumed downloads at once. Then send a fresh link for the new version.

Yes, on Scale and above: your logo, colour and a line of your own on share pages, portals and delivery emails, on a custom domain such as delivery.youragency.com.

No. Boita moves any file or folder as is, and a folder of many files runs as parallel sessions like anything else. Images, PDFs and video get previews; there is no DCP validation.

No. Boita moves and stores any file type as is. Images, PDFs and video get previews; model and point-cloud viewers are not planned.

In the desktop app, the transfer waits and resumes from its checkpoint when the link is back. Nothing already uploaded is sent again.

Yes. On Scale and above, folder permissions give a member or group view, download, upload or manage rights on one folder and nothing else. On any plan, share links and portals give outsiders access to exactly one folder.

Yes. The desktop app ships as an AppImage, and the headless boita-agent runs watch folders on a server under systemd.

Yes. Use boita upload and boita share from the CLI, or the REST API with a TypeScript or Python SDK (Pro and above); a signed webhook tells you when the publisher downloads.

No per-file cap; your storage quota is the limit. Pro includes 1 TB, Scale 10 TB and Enterprise is custom.

Yes. The headless boita-agent runs watch folders under systemd, controlled from the web app, and the desktop app ships as an AppImage.

No. Recipients of a share link need no account or seat. Seats are for members of your workspace who upload and manage files.

Yes. Previews render on the share page for images, PDFs and video. Recipients download at full speed through the free Boita app, or in the browser with nothing to install on the slower HTTPS path.

No. A folder of thousands of RAW files runs as parallel sessions like any other transfer; your storage quota is the only limit.

Add a password and a download limit, turn on recipient verification so only the named email can open it, and revoke the link when the job is done. Watermarked previews and downloads are on Scale and above.

Yes. Boita for iOS and Android uploads photos and videos as originals over HTTPS at standard speed, and “Send from my computer” picks files on your Mac or PC from the phone and has the desktop app send them on the fast path.

No. Boita moves any file or folder as is. It does not transcode or alter audio.

Add a password (Pro and above) and a download limit, and turn on recipient verification so the engineer confirms their email with a one-time code before the files are shown.

An interrupted transfer never re-sends completed files. Sending a folder again today creates a new transfer; skipping files already on the server by checksum is on the roadmap.

Yes. A portal link needs no account or plan. The page offers the free Boita desktop app for full speed and resume, or a browser upload with nothing to install: slower, and an interrupted upload starts again.

It provides the evidence for one: a server-recorded checksum on every file, a delivery receipt naming who downloaded what and when with a CSV verification report (PDF on Scale and above), and a per-workspace audit log.

Yes. They open the share page, enter the password if you set one, and download: in the free Boita desktop app at full speed with resume, or in the browser with nothing to install, slower, where an interrupted download starts again.

Support works from metadata, and with sender-side encryption nobody at Boita can read the files. Break-glass access to unencrypted contents will require a ticket, a second approver and a time limit, and appear in your audit log; this process is being built.

Yes, on Enterprise: export the audit log or stream it to your SIEM, and produce a legal-hold export package for a matter. On other plans the log is viewable in the workspace.

No. Files move and are stored as they are, with a checksum recorded on arrival. Boita does not compress, index or interpret them.

It needs outbound access to Boita on the fast path (UDP) or, failing that, HTTPS. Many facilities allow that from the acquisition server alone; the Linux agent sends from there and a download watch folder feeds the cluster.

Yes. A signed webhook fires when a portal upload or a transfer completes, and boita wait-receipt blocks in a script until every invited recipient has downloaded a delivery.

Yes, as long as they are relative. Boita keeps the folder layout and file names exactly, so references that resolved on your file server resolve on the supplier’s. Absolute paths to your own server will not, as with any copy.

No. Boita moves and stores any file type as is. It previews images, PDFs and video; model and point-cloud viewers are not planned.

The upload replaces the file and the previous copy is kept as a version for the retention window. Restore or delete any version from Files.

Yes. On any plan a sync rule copies each file landing in a workspace folder to the customer’s S3-compatible, Google Cloud Storage or Azure Blob bucket; Enterprise auto-delivery adds transfer servers, a delivery log and a webhook per file.

No. Tiles move and are stored as they are, with a checksum recorded on arrival. Boita is the delivery path, not a processing step.

A numbered set shows a gap warning if a tile is missing, and the delivery receipt lists every file with its checksum and whether the download verified.

No. Plans are flat monthly amounts sized by storage, retention and seats; no per-GB transfer fees and no charge for downloads.

Yes. The REST API is described in OpenAPI with TypeScript and Python SDKs, scoped API keys and a webhook console with test and retry, on Pro and above. The boita CLI ships with the Linux agent.

The desktop app or agent groups new files into batches of up to 500 and sends each batch as one transfer. Your storage quota is the only limit on count.

No, files land in the workspace first. On any plan, a sync rule then copies each one to your S3-compatible, Google Cloud Storage or Azure Blob bucket as it lands; on Enterprise, auto-delivery also pushes to an S3-compatible bucket.

No. It has no snapshots, no deduplication and no bare-metal restore. It is a fast, verified copy from your server to Boita and to a second site, with versions, an archive tier and checksums, alongside the backup software you already run.

No. Upload watch folders only send; download watch folders only fetch and never delete locally. Deletions are not mirrored in either direction.

Download from the web app, the desktop app or the CLI at line rate, or let a download watch folder rebuild the tree on a fresh server. Files in the archive tier are restored on demand first, with the restore time shown.

Yes. A portal link needs no account or plan. The page offers the free Boita desktop app for full speed and resume, and a browser upload with nothing to install: slower, and an interrupted upload starts again.

Not in the prepress sense. Portal forms check file type, name and count before an upload starts, and delivery specs flag files that do not match the spec on arrival. Fonts, colour profiles and bleed are still checked in your prepress software.

Yes. Branded portals and share pages, and a custom domain such as uploads.yourstudio.com, are on Scale and above; certificates are issued for you.

It depends on your line and the route. The calculator on the home page models TCP over your chosen route against Boita at your line rate and states its assumptions. Your plan’s session allowance and the far end are the real ceilings.

No. Recipients download from a share page and clients upload through a portal without an account or a plan.

Yes. Indian subscriptions are billed in INR with GST invoices and a GSTIN field.

Yes. Files, the transfer server, the application and the database run in Google Cloud, Mumbai, with encrypted backups in Mumbai and Singapore. The Trust page lists every location and sub-processor; DPDP Act obligations are reflected in its retention table.

No. Each upload is isolated in its own inbox folder on a token that can write to that folder only, in one direction, for a few minutes.

No per-file cap; your storage quota is the limit. Storage usage is shown on every page with an alert before you reach it.

Yes. Both the workspace owner and the uploader receive a completion email, and the upload is recorded in the workspace audit log.

Yes, on Scale and above: your name, logo, colour and a line of your own on every upload page and email, and the portal on a hostname of yours such as uploads.yourcompany.com.

No. State is kept locally, so the desktop app picks up where it stopped and completed files are never re-sent.

Hours, yes: a watch folder sends only between the hours you choose, and a workspace bandwidth window caps transfers during office hours. Include and exclude patterns by file type are coming; today a watch folder sends everything that lands in it.

No. Each watch folder is one-way: an upload watch folder sends local files to a workspace folder, a download watch folder pulls a workspace folder to a local one. A deletion on one side is never mirrored to the other.

Yes. The headless Linux agent runs watch folders up and down from the shell under systemd, and ships with the boita command-line client for scripts.

Correct. Plans are flat. Downloads and re-downloads are free. Lower plans carry a fair-use transfer allowance; if you are consistently far above it we talk to you about the right plan before anything is limited.

Storage included in the plan, share retention, seats and how many parallel sessions a transfer may use. API keys and webhooks start on Pro; Enterprise adds a dedicated bandwidth lane, SSO and auto-delivery to your own servers.

From a public price list of a per-GB service, summarised in our product specification: US$0.25 per GB and storage metered after a few free days. Those terms change; check the service’s own page for current figures.

Yes. Every workspace starts on Free with 10 GB and share links, with nothing to install; upgrade when you need the desktop app, portals or more storage.

It depends on your line and the far end. The calculator on the home page models an ordinary TCP upload over your route against Boita at your line rate and states its assumptions.

Yes. Start the transfer from the desktop app in the evening; it runs in the background and resumes if anything drops. A watch folder can be limited to chosen hours, and a workspace bandwidth window caps transfers during the day.

Boita falls back to an HTTPS path automatically. It is slower but still encrypted, and the app shows which path is in use.

Yes. On Scale and above, finished folders move to an archive tier with a manifest and come back on demand. A verifiable cold tier on decentralised storage is coming, on request.

No. Recipients download and portal uploaders upload straight from the browser over the standard HTTPS path, where an interrupted transfer starts again; for very large sends the page offers the free Boita desktop app for full speed and resume.

Yes. Upload the folders as they are; Boita keeps the tree, and members browse it in the Drive with search across every folder.

Yes. The boita CLI uploads, downloads, lists and shares from a script, the headless Linux agent runs watch folders under systemd, and scoped API keys with signed webhooks are included from Pro.

Boita falls back to an HTTPS path automatically when UDP is blocked. It is slower but still encrypted, and the app shows which path is in use.

An open link can be forwarded, which is why passwords, download limits and revocation exist. Recipient verification on Pro and above restricts a link to named, code-verified email addresses, which closes that gap.

Support works from metadata. Break-glass access will require a ticket, a second approver and a time limit, and appears in your audit log. With sender-side encrypted delivery we never hold the passphrase, so we could not read the files at all.

Two-factor authentication and passkeys are live per account. A workspace policy that enforces it for all members is coming; on Enterprise, members can sign in through your own identity provider with single sign-on.

Not yet. Boita does not claim a certification. SOC 2 Type II is in progress, a penetration test follows, and industry assessments are being pursued. A written security programme is available on request.

No. An upload watch folder at one office and a download watch folder at the other move files in one direction each; nothing is deleted on either side. Two-way sync is on the roadmap.

Yes. Each machine with the desktop app can run watch folders into folders you choose. Pro includes two watch folders and Scale has no limit.

The desktop app holds whatever line rate the site has and resumes after every drop. Limit the watch folder to chosen hours and cap daytime transfers with a workspace bandwidth window, so the site connection stays free during the day.

Yes, on Enterprise: pair a workspace folder with your own transfer server or S3-compatible bucket and every file that lands is pushed there within minutes, retried on failure. On other plans a download watch folder does the job from the receiving machine.

For full speed and watch folders, yes; it is included from Pro for macOS, Windows and Linux. The web app covers browsing, sharing and workspace admin, and the browser path works with nothing installed, more slowly.

From the desktop app, yes: the transfer resumes after every drop and never re-sends completed files. If the hotel network blocks UDP it falls back to HTTPS automatically. A browser upload starts again.

Yes. Remove the member from the workspace, or if they worked through links and portals, revoke those links; download tokens expire in minutes, so revocation is immediate.

No. Plans are flat; there are no per-GB fees. Lower plans carry a fair-use transfer allowance, and if you are consistently far above it we talk to you about the right plan before anything is limited.

A cryptographic proof, produced by the archive storage provider at intervals, that the data is still being held as agreed. Boita records it on the file record for archived items.

No. Hot storage on the transfer nodes is where every transfer lands and where files are downloaded from. The archive tier is an optional cold destination for aged data; decentralised storage is one backend for it, and India-residency workspaces use a domestic object store instead.

It is not instant. The expected restore time is shown when you request one, and the files return to hot storage.

It is priced as a separate cold tier, lower per terabyte than hot storage, and quoted on request when it ships. Prices are not yet announced.

No: Free has 10 GB of storage and two sessions at 10 Mbps. 100 GB needs Pro, with 1 TB of storage and the desktop app.

No. They open a page and download in the browser; the free app is optional.

In the desktop app it resumes by itself where it stopped; from a browser or the phone app it starts again. Completed files are never re-sent.

No; your plan’s storage quota is the only limit.

No. Files already on the server are skipped, and in the desktop app a part-sent file continues from its checkpoint.

The download cannot resume. Tokens are minted per download and expire in minutes; revoking the link stops new and resumed transfers immediately.

Yes. The checksum is recorded on the complete file at the end of the transfer, however many sessions or reconnects it took, and verified on every completed download.

No. In a browser, an interrupted upload starts again from the beginning; in a job of many files, the ones that finished stay finished. For large files, use the desktop app, which picks up where it stopped.

No. They receive a link and open a page, as before, and download without an account; the free app is optional.

Yes. Upload the folders as they are from the desktop app, or import from an S3-compatible bucket; Boita keeps the tree.

No. The web app uploads from the browser over the standard HTTPS path; the desktop app is there when speed and resume matter.

Yes. Free has 10 GB, share links with expiry and the sender dashboard.

No. Egress is billed by your cloud provider whatever tool moves the data; Boita adds no per-GB fee of its own.

No. The import runs on our servers into your workspace; the pull runs from the app, the agent or the CLI on your server.

No. The import lands in your workspace first, which gives you the checksum and the audit trail; plan storage applies while it is there.

Yes, both, through their own APIs: a service-account key for Google, a connection string or SAS token for Azure.