The community plan has limits for storage and does not support offline editing for PostGIS layers. You can still have unlimited private and public projects.
#qfieldcloud #plans

There is no limit to the number of collaborators for public projects.
#qfieldcloud collaboration #plans

This is exactly how QFieldCloud works as long as your project is public. If you need the same functionality in a private project, you must create an organisation.
#qfieldcloud collaboration #plans

On the Flat plan, all organisation members are billed each month regardless of activity. On the Flex plan, only members who actively use QFieldCloud that month are billed, with a minimum of 1 billed user.
#qfieldcloud #plans

You can work with live PostGIS layers with any plan. If you need offline editing, you would need to be on a paid plan.
#qfieldcloud #plans

On the Flat plan, each user includes 1 GB of sync space, pooled at the organisation level. On the Flex plan, the organisation includes 1 GB. Additional storage is billed at the organisation level at €5 per month per 3 GB. For example, if you need 10 GB total on a Flex plan, you have 1 GB included and need 9 GB extra (3 blocks of 3 GB), which costs €15/month.
#qfieldcloud billing #plans

The storage is the sum of the size of all files in all projects that are owned by the account.
#qfieldcloud storage plans #billing

There is no restriction on file size. However, we recommend keeping files of sensible size (e.g. up to 1 GB), as bigger files might be hard to download with an unstable internet connection.
#qfieldcloud storage plans #billing

No, this is not planned. It's, however, possible to collaborate freely on public projects. It is also possible to create a trial organisation for 28 days to explore its features.
#qfieldcloud #billing

Credit card is supported for both monthly and yearly billing; yearly is set up directly in the app. If your organisation needs to pay by bank transfer, you can request a manual invoice here.
#qfieldcloud #billing

QFieldCloud GmbH is a registered company in Switzerland.
#qfieldcloud #billing

No, for now, all payments are only in EUR.
#qfieldcloud #billing

Both monthly and yearly billing are available. Yearly billing by credit card is set up directly in the app. If your organisation needs a yearly invoice paid by bank transfer, you can request one here.
#qfieldcloud billing #sales

Yes, organisations get 28 days free of charge. Individual users can use the community plan for as long as they want.
#qfieldcloud billing #sales

Yes. On the Flat plan, the rate drops to €14 per user per month from 20 users when billed annually. For larger teams or custom requirements, get in touch.
#qfieldcloud billing #sales

QFieldCloud is open-source, and you can run it on your infrastructure. Check out the QFieldCloud GitHub repository for instructions on how to get it running. If you need premium support and app.qfield.cloud running on your infrastructure, we can add you to our interested customers' list, and after releasing QFieldCloud, we can come back to you with all the required information.
#qfieldcloud #sales

Yes, any registered user can download a public project and open it in QGIS. Make sure not to save your database credentials in your QGIS project when using a community account. Per default, when someone downloads another person's public project without being added by the person as a collaborator, he or she will only have a Reader's permission. You can, however, add collaborators explicitly to your public project and select other roles for them.
#qfieldcloud #collaboration

All data is stored on servers hosted in Switzerland.
#qfieldcloud #datacenter

The shared service is hosted in Switzerland. Dedicated Enterprise instances can be hosted in Switzerland, the EU, or Canada, with additional locations available on request.
#qfieldcloud #datacenter

Yes, this is possible with an organisation on the Flat or Flex plan.
#qfieldcloud #collaboration

Yes, a collaborator first needs to be added as a member of the organisation. Members can then be added to specific projects.
#qfieldcloud #collaboration

Private project collaboration requires a Flat or Flex plan. Members of an organisation can collaborate on all projects owned by the organisation.
#qfieldcloud #collaboration

No, they are not. QFieldCloud is a platform that allows data synchronisation for seamless fieldwork. QGIS cloud is a publishing platform by a different company.
#qfieldcloud

Any account type works. As soon as you are added to an organisation as a member, the organisation is billed for you. All organisation members are regular users, regardless of their permissions (reader, editor, administrator, etc.). For your own projects, you can use the free Community plan.
#qfieldcloud

Yes, this is exactly what QFieldCloud is made for and how it works.
#qfieldcloud #collaboration

We don't have a single page for details on features in future versions at the moment. QField has an integrated changelog screen when a new QField version is released. We will consider communicating on a roadmap. In the meantime, you can follow the development of QField and QFieldCloud on GitHub.
#qfield #qfieldcloud

Yes, working offline is possible. You can configure your PostGIS layers as "offline editing" and synchronise your project once you are connected to the internet again.
#qfield #qfieldcloud

Yes, they are two different applications. QField is a mobile app for field data collection; QFieldCloud is a platform that allows data synchronisation for seamless fieldwork. If required, QField can be used without QFieldCloud.
#qfield #qfieldcloud

QFieldCloud officially supports PostGIS and GeoPackage data source formats. While QFieldCloud will most likely work with your other data format, they are not officially supported.
#qfield #qfieldcloud

We don't have a fixed discount for charities or non-profit organisations yet; please check the special pricing page to get in touch with us to explain what you do and what you need.
#qfieldcloud billing #sales

Yes, we take academic usage very seriously, that is why we offer a full-blown heavily discounted package with all options included.
For pricing details and to apply for an academia plan, please refer to the academia page
#qfieldcloud collaboration #plans

Unfortunately, not yet for GeoPackage layers. You have to wait for fieldwork to finish before synchronizing and editing on QGIS, or you have to merge GeoPackages from QFieldCloud and your QGIS file manually. We are working for a solution for this inconvenience.
#qfieldcloud

1. Check Data Format Compatibility: Ensure that your data is in a recommended format, such as GeoPackage (.gpkg) or PostgreSQL. Using incompatible formats can cause issues with data and synchronization.
2. Sync Local Changes with Cloud: Verify that your local changes are synchronized with the latest version of the QFieldCloud project.
3. Navigate to the Project Path: Open the project from its designated path in your file system. Typically, this would be located at ../{user}/QField/cloud/{Project name}/. Navigating directly to the project path ensures you're working with the correct files and directories.
4. Confirm Changes were applied Successfully: After pushing changes from QField, confirm whether they were successfully applied and checking data in the changes section of QFieldCloud.

#qfieldcloud