Starting with the good:
-The platform is VERY clever and intuitive!
-It is set up like the traditional convention model in physical spaces, but in a digital 2d space.
-It's quite easy to navigate for the user once you get used to it, the navigation is logical. The team has done a very good job capturing the most essential features a physical convention has going on.

I haven't played with it enough to see what it can handle. Some people are talking about lags and not being able to handle too much.

The team themselves recommend caps, while still saying this is 'unlimited' - this is a bit of a red flag. I hope this 'recommended cap' is temporary while they build out their infrastructure and perhaps migrate to a more powerful server, or set specific limits and remove the 'unlimited' wording to be very clear on limits.

I am VERY close to requesting a refund for all of my 3 codes, but am still waiting on proper responses from the many outstanding questions.

1) Registration count. The answers from the team are still quite vague, even though they are saying complete statements, they are not responding to the use case itself.

I have a use case of wanting a lounge open 24/7 for members. I'm OK if it's open for 365 days and users have to re-register once a year.

The response was: [B]: Registration will be counted monthly basis

QUESTION: Is this NEW registrations being counted on a monthly basis?

Let's take this situation one step at a time:
1. Event is set for 365 days.
2. Month 1 has 10 registrations
3. Month 2, there are 10 people ALREADY registered from Month 1, and 10 more people register.

There are one of two ways this could potentially be counted:
a. Month 2 has 10 registrations, because there are NEW registrants
b. Month 2 has 20 registrations, because it's counting the Month 1 registrations

HOWEVER, do the Month 1 users have to RE-REGISTER? Wouldn't they be considered attendees??

This response by a user in response to the creator talking about 'gaming the system' captures my sentiments exactly:
"Re:
“
However, this functionality can clearly be gamed by other communities who're doing paid events and are trying to host a much larger number of participants throughout a month. So, to address this issue, we'll have to put a limit on how long (in days) an event can run non-stop. Honestly, we haven't come up with that final event duration yet, it could be 5 days, 7 days, or more.
“
May I suggest Airmeet fixes this so the functionality can not be ‘gamed’?
Be clear. Don’t remove the cap, as it something people have bought this deal based on; ‘no cap’.
Awaiting Airmeet’s prompt response.
Appreciated.
Best,
Mark""

2) User count
Response from team: The 1 code plan included 2 users - 1 is the purchaser and 1 additional team member.
Another user said: Uktarsh told me below that "In the 1 code deal it's just the community manager. So, only 1 user. Yes, you can won't be able to run parallel session with just 1 code." You say it's 2. Which is right?