[FEATURE] Table view for the Add Service page and maybe also CLI

[EhudKirsh]

Is your feature request related to a problem?
Well, it relates to #215 because I want to be able to switch from and to any protocol that any cloud drive supports in its Quick Connect page.
This post is about doing so in the Add Service page when setting up new profiles, while #215 is about doing it when editing existing profiles.

Describe the solution you'd like
I'd like the Add Service page to have a Table view just like the My Servers page. Perhaps also have it in aeroftp-cli, just like aero profiles.
I like the ability to view all cloud drives in one table without having to go through the tabs that are currently in grid view.
Please keep grid view as it is, just also add this optional table view to the Add Service page just like in the My Servers page:

Country Flag	Company	Amount of free storage (GB)	Free-tier account without a credit card	Paid-only or required credit card account 💳
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	Cloudinary	25	Cloudinary API	-
🇮🇳	ImageKit	20 (or 25?)	ImageKit API	-
🇯🇵	InfiniCloud Co. Ltd.	20 (or 25?)	InfiniCLOUD OAuth API WebDAV	-
🇫🇷	Drime	20 (or 21?)	Drime API	Drime for Enterprise
🇳🇿	MEGA	20	MEGA (& S4) API MEGAcmd WebDAV S3	-
🇺🇸,🏴󠁵󠁳󠁴󠁸󠁿	Oracle Corporation	20	-	Oracle Cloud S3
🇳🇱	PixelUnion	16	PixelUnion API	-
🇨🇭	Infomaniak	15	kDrive API WebDAV	-
🇺🇦	4shared	15	4shared OAuth WebDAV SFTP FTP	-
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	Alphabet Inc.	15	Google Drive OAuth	Google Cloud
🇨🇿/🇩🇪	S3Drive	12	S3Drive S3	-
🇩🇪	Filen	10	Filen API WebDAV S3	-
🇨🇭	pCloud	10	pCloud drive Individual OAuth WebDAV	pCloud drive Family/Business
🇸🇮	Koofr	10	Koofr API WebDAV	-
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	Box	10	Individual OAuth	Business/Enterprise
🇪🇺	Felicloud	10	Felicloud Free Account WebDAV	Felicloud Business Cloud WebDAV
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	Cloudflare	10	-	Cloudflare R2 S3
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	IDrive Inc.	10	-	IDrive e2 S3
🇪🇺	Tab.digital	8	Nextcloud Tab.digital WebDAV	Nextcloud for Business WebDAV
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	OpenDrive, Inc.	5 (+2)	OpenDrive Personal API WebDAV	OpenDrive Business & Enterprise
🇳🇴	Jottacloud	5	Jottacloud API	Jottacloud for Business
🇷🇺	Yandex	5	Yandex Disk OAuth WebDAV	Yandex Object Storage S3
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	DriveHQ	5	Personal WebDAV	Business WebDAV SFTP FTP FTPS
🇮🇳	Zoho	5	WorkDrive OAuth	WorkDrive Enterprise
🇺🇸,🏴󠁵󠁳󠁷󠁡󠁿	Microsoft	5	OneDrive OAuth	Azure Blob
🇨🇳	Alibaba	5	-	Alibaba Cloud OSS S3
🇸🇪	CloudMe	3	Consumer WebDAV	Business/Enterprise WebDAV
🇺🇸,🏴󠁵󠁳󠁣󠁡󠁿	Dropbox, Inc.	2	Dropbox OAuth	Dropbox Enterprise
🇺🇸,🏴󠁵󠁹󠁦󠁤󠁿	FileLu, LLC	1 (+20)	FileLu (& S5) API WebDAV FTP FTPS S3	-
🇪🇸	Internxt	1	Internxt API WebDAV	Internxt object cloud storage S3
🇪🇺	UploadCare	1	Free/Pro API	Business/Enterprise
🇺🇸,🏴󠁵󠁳󠁷󠁡󠁿	Amazon	0	-	AWS S3
Total	32	319	27	21

Describe alternatives you've considered

• I have considered making the last 2 cols into simply accounts with free-tier storage, and ones without. This would move Oracle Cloud, Cloudflare R2, IDrive e2 and Alibaba Cloud OSS one col to the left with the rest of the free-tier cloud drives. I dislike this idea because they're all cloud drives that require linking an up-to-date credit card to be able to use them, which feels out of place with the rest of the free-tier cloud drives. I feel that they belong more with enterprise cloud drives, which they technically are.
• I don't see alternatives for having a table view, but I can imagine a different set of columns. I was thinking initially to make a col per protocol, and merge some cells with colspan, but I showed here the simpler approach and simply making these into badges. The issue is that 4shared supports FTP and SFTP, while FileLu supports FTP and FTPS, so there's no nice way to merge around it as I see it, no matter how you sort the cols, unless FTPS shares a col with FTP, or even SFTP. It's also possible to solve by splitting such cloud drives into 2 groups of merged cells. If you do decide to implement this approach as an alternative, which I think could be nice, possible and even preferred by some users, this will require the free-tier and enterprise cloud drives of the same companies to be in separate rows, because they often use the same protocols.

Additional context

• I decided to open this as a new post instead of continuing in [BUG v3.8.2] Can't switch protocols when editing Filen profiles #215, because this is moving from a bug fix to a feature request, so it felt out of scope there. I was actually waiting for the next wishlist to raise this idea, but it feels better to raise it now to address [BUG v3.8.2] Can't switch protocols when editing Filen profiles #215.
• I made this <table> in HTML, so you can click on ... at the top-right of this comment and "Copy Markdown" to take this table straight to the GUI, and also to https://www.aeroftp.app or https://docs.aeroftp.app if you like.
• This table is sorted descendingly from the cloud drive that offers the most amount of free-tier storage to the least. I think this should be the default, and users should be able to sort ascendingly and descendingly, and their last sort should remain as their preference and be backed up to .aeroftp-keystore.
  • Besides sorting the 'Amount of free storage (GB)' col ascendingly and descendingly, all other cols should also be possible to sort alphabetically.
  • Where cloud drives equal in the amount of free storage, I sorted by other things like not requiring a credit card 💳 and ease of setting up the connection.
• 🔍 There should be a searchbar to filter by strings, including by badges/protocols, just like in the My Servers page.
• It should be possible to hide and unhide cols just like the Table view in the My Servers page with a dropdown menu.
• I included the state emojis for US companies out of curiosity. They likely render as black flags 🏴.
• I didn't include the logos here, but you can imagine that they should be added just like they look in the current grid view. You can also include company logos if they are different than their cloud logos. It really depends on what looks better.
• You can add more cols. I was thinking about maybe another on how much storage each offers via referrals and leaving a review. I currently didn't show referrals at all in the table, and only showed in brackets the additional storage from leaving a review and didn't take it into the calculation.
• Custom profiles like WebDAV, S3, FTP/FTPS, SFTP, etc, can be listed below the table.
• What I love about this table view is that it's a definitive place to see once and for all, the total (uncompressed) amount of free storage of the cloud drives that AeroFTP supports, and the number of cloud drives that have free tiers as well as paid-only. I'd like the footer to be dynamic and calculate the total based on filters. I want to see for example the total free storage and number of cloud drives with 2GB or more, that don't require a credit card 💳 which AeroFTP supports. That will be interesting to see. So hiding the last col will also hide the free storage from cloud drives that require a credit card, and the footer will update dynamically.
  • If you want to make each protocol into its own col instead of a badge, the footer can be a counter of the total number of cloud drives that support each protocol. Then again, this would be possible even with badges, by searching let's say "S3" in the searchbar 🔍,
• Right now each protocol badge has a different colour in the My Servers page, and also in Add Service > ☁ Cloud Storage. Let's try something slightly different in this new Add Service Table view - have 2 colours: yellow/orange like the current S3 for protocols that are only unlocked for paying clients, and another colour like blue that are included in free-tier.
• Please notice that every badge represents a protocol option, and therefore, another radio button for [BUG v3.8.2] Can't switch protocols when editing Filen profiles #215. So for example, there're 2 options for Yandex Disk, 3 for Filen, 4 for MEGA and 5 for FileLu.
• Besides being able to enter the Quick Connect page of any cloud drive by clicking on its rectangle, also be able to click on any badge to enter directly with that protocol selected.
• This table is obviously just a draft, and I know it has some rows and badges missing, but it's for simplicity of course. If you wonder how I calculated the total storage, I decided to go on the safe side and assume the least amount of storage here. So the total storage capacity here is an underestimate, and would be even less for users that don't want to give away their credit card details and not bother with cloud drives that provide a small amount of storage like under 2GB. Here's the exact calculations to save you time if you wish to verify it: 25+20*5+16+15*3+12+10*7+8+5*7+3+2+1*3. Counting the number of cloud drives was easy, just search for the number of occurrences of <tr><td> in an IDE.

Notes on protocols that cloud drives support that you might want to add/pre-configure in AeroFTP:

• Reminder: pCloud Drive with WebDAV, not only OAuth. Similar to Yandex Disk.
  Recall [WISHLIST] v3.8.0 wishlist: share your enhancement suggestions #180 (comment).
• FileLu with WebDAV - https://filelu.com/pages/cloud-drive, and FTP & FTPS - https://filelu.com/pages/cloud-storage-ftp-server.
• 4shared premium support for FTP and SFTP: https://www.4shared.com/features.jsp.
• kDrive's paid WebDAV: https://www.infomaniak.com/en/support/faq/2409 - I personally tried WebDAV with a free tier, and it didn't work.
  An Infomaniak employee confirmed to me over email on the 26th of December 2025 that WebDAV is a paid feature.
• Internxt's "Ultimate" paid tier WebDAV: https://internxt.com/pricing. I think this might require using its CLI similar to webdav / in MEGAcmd.
  Also https://internxt.com/cloud-object-storage for the S3 / Object Storage tab.
• InfiniCLOUD's REST API and support of OAuth: https://infini-cloud.net/en/developer.html.
• Drime's planned WebDAV: https://drime.notion.site/roadmap?p=2b254b78f84a81d7879be462d9de7f61.

More notes on specific cloud drives:

• I wrote that ImageKit and Cloudinary each offers 25GB of free-tier storage since that's what I see under 'Digital Asset Management' in https://cloudinary.com/pricing & https://imagekit.io/plans. Not sure if you tried it, I plan to try it at some point.
• OpenDrive doesn't seem to say where they're headquartered on their website, but I found this: https://pitchbook.com/profiles/company/87112-36

[axpnet]

Thanks for the very detailed write-up and the ready-to-copy HTML table, Ehud. This is a solid discovery feature: a single comparison surface for picking a provider, separate from actually connecting to one. I like it, and I want to do it.

One quick note on scope. AeroFTP already has a "Providers & Integrations" panel (View > Providers), but that one answers a different question, namely what each provider can do once connected (upload, share links, trash, versioning, and so on). What you are describing is a discovery and comparison view, "which provider should I pick", and that is genuinely a different surface. I will treat it as its own thing and keep the current grid view exactly as it is, as you asked.

There is already a head start on the data. The documentation site carries a comparison table that is close to what you sketched:

• A "Pricing Snapshot" table on https://docs.aeroftp.app/providers/ with the columns Provider, Category, Tier Snapshot and Notes.
• A small badge taxonomy reused everywhere: FREE, TRIAL, PAY, CARD, SELF-HOST, BYO, LOCAL. The CARD badge already encodes exactly your "free tier or trial normally requires a credit card" column.
• Every individual provider guide opens with a per-provider "Plan snapshot" using the same markers.

So the in-app table would build on that existing taxonomy and dataset, which keeps the app and the docs consistent and gives me a single place to maintain the figures.

On the caveats you raised, which I agree with:

• Free-storage totals drift. I agree, and I will not present an authoritative "definitive total". Free tiers change at each provider's discretion, and several entries in your draft are already uncertain ("20 or 25?"). The docs table handles this by being explicitly dated ("Pricing Snapshot, May 2026"), and I would do the same in-app: the figures are a point-in-time snapshot, with each provider's own signup page one click away as the real source of truth. A dynamic footer total is appealing, but if I keep it I would label it clearly as approximate rather than as a headline number I guarantee. I would rather under-promise here than show a precise-looking total I cannot keep perfectly current.

• The credit-card / paid-only column is editorial. True, and you debate it yourself in your "alternatives considered" section. I will keep it, expressed through the existing CARD badge, and I own that it is a curated judgement.

• Country flags. This one is solvable, good news. Emoji flags would indeed break on Windows (they render as letter pairs), but AeroFTP already shows SVG country flags in Settings (the language selector uses the country-flag-icons set), and those render correctly on every OS, Windows included. The flag column would use that same approach, not emoji.

On the structure. The in-app provider catalog is currently organized per protocol and per preset, spread across categories, so the same company can appear as several entries (MEGA as native and as S4, FileLu as API, WebDAV and S3, and so on). Your table is organized per company, one row, with the protocols as badges. That is the nicer model for this view, and it also lets each badge double as a quick entry point straight into Quick Connect with that protocol preselected. It does need some restructuring on my side, but it is worth it.

On the link to #215. In the Add Service page nothing is saved yet, so clicking a badge to start a new connection with a given protocol is unproblematic. That is different from switching the protocol of an already-saved profile, which is the constrained case in #215 (some cloud modes are separate backends and cannot be swapped in place). So #224 complements #215 rather than depending on it.

Sorting, the searchbar (including search by badge or protocol) and hide/show columns would follow the same behaviour as the My Servers table, for consistency.

Two questions for you before I commit to a shape:

1. Would you be happy if the in-app table leaned on the docs badge taxonomy (FREE / TRIAL / PAY / CARD) rather than, or alongside, the raw GB numbers? The badges age much better than exact figures and avoid the "is it 20 or 25" problem.
2. The dynamic footer total: keep it, clearly marked as an approximate snapshot, or drop it to avoid implying a precision I cannot maintain? I lean towards keeping it but labelled as approximate. Your call as the person who most wants that number.

This is a wishlist-tier enhancement, so no version lock: I will fold it into a wishlist cycle. Thanks again for the thorough proposal, the HTML table is genuinely useful as a starting dataset.

[EhudKirsh]

Thank you for considering my idea.

Sorry, I'm on my phone and it accidentally closed this issue and submitted this comment before I finished it.

1. I must say, I'm not a fan of seeing the FREE / TRIAL / PAY / CARD badges myself, but there's an easy solution: consider having 2-3 table structures like the alternatives I wrote that can be switched between, with filters of showing and hiding any badge, col, rows below certain amount of storage, etc. This can be an interactive page where users only see the cloud drives and protocols/badges that they find interesting to prioritise making accounts and connecting with them.
   
   For example, I'm not interested in trials, so I would prefer being able to not see such a TRIAL badge, so please just have a dropdown list filter that hides it. I think the PAY badge is redundant and obvious, they're all businesses, except for maybe a couple of self-hosting solutions like Nextcloud. FREE and CARD are just the last 2 cols in the <table> I made, so I'd like to not see them personally, and even be able to hide that last col in fact. This would give users with my particular preferences the ability to see only the protocols as badges. Also, I prefer seeing 💳 instead of CARD.
   
   Regarding emojis, I only use them here because it's easier, but of course, in the app it makes sense that you use SVGs that look like emojis.

2. I definitely prefer keeping the Total footer. It's approximate, that's fine. Feel free to inform the user in small text under the footer or what not.

[axpnet]

The shipped table already covers all three:

• No FREE / TRIAL / PAY / CARD text badges: there is a single Free / Free+card / Paid tier filter in the toolbar instead (parity with the CLI catalog --free/--paid).
• The credit-card requirement shows as a small 💳 icon next to the free-storage figure, not a "CARD" word.
• Columns are individually hideable and reorderable from the Columns manager, so you can turn off everything except the protocol badges.
• The footer Total is kept and labelled approximate.

[EhudKirsh]

Another thought on why I'm not a fan of the PAY badge:

• It can have a bad connotation for those starting out and wanting to try free cloud storage.
• If the opposite of a cloud drive that accepts money is always self-hosting, then it should be obvious just based on the col that writes how much free storage a cloud drive offers, that a cloud drive that offers any free storage at all isn't self-hosting. Some protocols like SFTP, WebDAV, etc, could be for self-hosting or cloud drives hosted by companies, but that's why such custom profiles using these protocols should be listed below the table. My point is, that it's obvious that, for example, PixelUnion, Felicloud and Tab.digital aren't self-hosting, while Nextcloud and Immich are, just based on whether any offers free storage and even which col it's in like in the case of enterprise object storage. So the PAY badge feels redundant as having 2 cols and sorting by the amount of free storage will be enough to accomplish this.

[axpnet]

Agreed, and that is how it shipped: there is no PAY badge. Paid-only reads from the free-storage column plus the gold "Paid protocols" column and the tier filter, exactly as you argued. Custom SFTP / WebDAV / S3 (which can be self-hosted or hosted) sit in the separate "Custom / generic servers" strip below the table, not as rows.

[EhudKirsh]

Thank you for implementing a table view for the Add Service page. Here’s my feedback on how it can improve over what it is now in v4.0.7:

1. Please rename 'List' to 'Table' when hovering over the table view button, and only show one of these buttons at a time (Grid or Table), like in the My Servers page.

2. Missing profiles to fill in:

   • 4shared is missing from the '🌐 WebDAV' tab in grid view.
   • S3Drive and Quotaless S3 are missing from the S3 tab in table view.
   • Rebex FTP Demo and Rebex SFTP Demo are missing from the Protocols tab in table view.
   • The FTP badge of FileLu should be added to launch it into Quick Connect directly in the FTP tab, which I already see it has.
     I suggest making an FTP tab. I expect there to be more cloud drives that support FTP, at least as a premium feature.
   • I also see that Blomp is missing from the '☁ Cloud Storage' tab in grid view, but if it's not ready yet, that's understandable.

3. Recategorise:

   • Remove Azure Blob from the CUSTOM / GENERIC SERVERS group. It's already with Object Storage where it should be.
   • Only show the relevant protocols in the CUSTOM / GENERIC SERVERS group based on the selected tab.
     So all of them should be shown only when selecting the All tab. When selecting S3, only S3 should show there.
     When selecting the bottom 3 tabs, CUSTOM / GENERIC SERVERS should not be shown at all. Alternatively,
     these can be the last row, with a colspan='2' over the free and paid cols, maybe in a different colour than blue or gold.

4. Missing or incorrect information:

   • Felicloud allows 10GB of free storage.
   • Tab.Digital allows 8GB of free storage.
   • Uploadcare allows 1GB of free storage.
   • Alibaba OSS allows 5GB of free storage, if we judge it by the same standard as Google Cloud and other cloud drives that require payment card details.

5. Please combine MEGA S4 to the same row as MEGA with API and MEGAcmd.

6. You can write "S4 (S3)" or "S3 (S4)" for MEGA, and likewise the same thing with FileLu and S5.

7. Please remove the part where the selected tab's name and icon are shown at the top-left, so the search bar and the buttons to its right can go up. The number of supported providers is also already shown at the bottom and the side on each tab, so it doesn't need to be in the top-left as well.

8. Please move any cloud drive's badge to the yellow 'Paid protocols' column if it requires credit card details to access the free storage.
   I think Oracle Cloud, Cloudflare R2, IDrive e2 and Google Cloud are specifically the ones that should change from blue to gold.
   This change should come with renaming the headers to something like "Free-tier without/Don't require a credit card" and
   "Paid-only or require a credit card 💳". Alternatively, to the right of CUSTOM / GENERIC SERVERS, you can write keys for the colours of badges like gold for protocols that are never free or require a credit card 💳, blue for those that don't, and white for generic/custom that can be either way, i.e. the CUSTOM / GENERIC SERVERS group.

9. I think there's an opportunity here, and also in the Quick Connect pages, to highlight the recommended protocols. Perhaps you can have an outline in a certain colour with a key for "Recommended". I'd recommend API over WebDAV for OpenDrive due to privacy. Although we should really run benchmarks before making any recommendations.
   
   I read https://docs.aeroftp.app/providers/backblaze-b2.html, and I’m glad that you wrote about the nuance between the native API of Backblaze B2 and S3, but I think you should add a word or two about Rclone and Kopia. I think they might handle the native API of Backblaze B2 and S3 differently and possibly have different recommendations due to possible shortcomings in their implementations of these. You might wish to explain and cite in https://docs.aeroftp.app/providers/backblaze-b2.html the following:
   o https://kopia.io/docs/repositories/#backblaze-b2
   o https://kopia.io/docs/advanced/ransomware-protection
   o https://www.reddit.com/r/backblaze/comments/vr0hzv/b2_native_api_vs_s3_compatible_api

10. Can you please include "Microsoft" in the provider name of OneDrive and Azure Blob? So if they don't share the same row, they can at least be seen next to each other when sorting alphabetically, like you can see being the case with Google Drive & Google Cloud and Yandex Disk and Yandex Object Storage. There's no need to add the company name Infomaniak to kDrive because that's the only cloud drive it has in AeroFTP, though you can for completeness. I do notice that GitHub is a provider in AeroFTP, and it's owned by Microsoft, so for completeness, I would think of asking to write "Microsoft GitHub" in the table view, but I'm not sure if it sounds quite as good as writing "Microsoft OneDrive" and "Microsoft Azure Blob". Maybe it's best to have an optional column for the companies if the name of the cloud drive differs from the company name, or if the same company has multiple services that AeroFTP supports.

[axpnet]

Thanks, this drove a batch shipping in v4.1.2 (tracker #384, rows 17 and 19).

Fixed now: single Grid/Table toggle labelled Table; the "Custom / generic servers" strip is filtered per tab and Azure Blob dropped from it (it has its own Object Storage row); Microsoft OneDrive / Microsoft Azure Blob now sort next to each other; Uploadcare corrected to 1 GB (you were right). Felicloud 10 / Tab.digital 8 / Alibaba OSS 5 GB, and the gold Paid column + 💳 marker for Oracle / Cloudflare R2 / Google Cloud / IDrive e2, were already in.

Kept on purpose: the category icon + name header at the top-left. It is the "you are here" indicator for the left-menu selection, and its row also holds the view toggle and health controls, so removing the label would not free vertical space for the search bar.

Planned: merging MEGA S4 into the MEGA row as "S4 (S3)" (S4 is a separate paid product with its own regions, so a proper multi-product merge, not a relabel); Rebex FTP/SFTP demos, S3Drive, Quotaless S3 and an FTP tab (these need real connection presets); the recommended-protocol highlight (after benchmarks, as you noted); and expanding the Backblaze B2 docs with the Rclone / Kopia nuance. Blomp stays hidden until its API is reliable, as you guessed.

[EhudKirsh]

One more thing: I'd like to ask for consistency regarding the order in which badges are sorted.
Right now WebDAV is shown before S3 for FileLu but it's the other way around for Filen.
I prefer the order that FileLu has, since the tabs have the order of S3 - WebDAV - API/OAuth, so WebDAV is in the middle.

[axpnet]

Fixed in v4.1.2 (tracker #384, row 17). Badges now sort native (API / OAuth), then WebDAV, then S3 for every company, so WebDAV sits in the middle and Filen matches the FileLu order you preferred.

[EhudKirsh]

Another correction: DriveHQ says 1 GB in the table view of the Add Service page,
but https://www.drivehq.com/help/Price/Cloud_IT_Service_Pricing_Personal.aspx says 5 GB.

[axpnet]

Fixed in v4.1.2 (tracker #384, row 17). DriveHQ now shows 5 GB, matching their personal plan page.