I am really impressed with your demo video, particularly the analytics, logs, and test suite features.
I'm a target customer where I have a few curious customers, but I'm not fully ready to roll it out yet across the customer base. One thing that's stopping me, what does credits mean on your pricing page? And what is the pay as you go price after you hit your limit? I would need to be able to budget this before I deploy.
The second piece - we already have a CLI, which is great for terminal based agents and what we will continue to recommend. What we really want, and I think is what you are offering, is basically an easier way to deploy a 'remote connector' to use Claude lingo so that normal users with the claude/chatgpt app can just use our MCP. Can you point me to guidelines or the right place in your open source templates to understand how I would best handle auth (or the tradeoffs in each) during the initial build phase of the MCP server?
Have you been able to nail down a loop where your tool can take an open pr, guess the code path and do some testing?
We use cypress heavily for our core flows which has a similar ai prompt thing but it’s not quite ad hoc enough for smaller fixes which is where the bottleneck still comes in for us.
First of all - totally agree. I work half-time so I get to spend extended time every day with the kids.
My post did not say anything about how I was going to use the computer, in fact we often do exactly what you said with his fake keyboard in between his other activities.
I also believe that it's my job to provide my children with the environment in which they can thrive and be independent. This post is asking for constructive guidance on how other people have navigated the transition into engaging with technology that all kids go through.
I have not really used Github Copilot out of concerns with IP; however, they recently added an IP indemnity clause that might have me take the leap. I use Jetbrains products (RubyMine) and would love to give this a shot instead.
Thanks for the reply. We do plan on taking another pass at analytics in July or August. I'll give the system user_id a try, it's entirely possible that will work for us and I have simply not gotten to an aha moment yet with the product (we are starting from scratch, so no segment data to import).
> I'm not sure why this is completely blocking you, we have plenty of customers that just create a user with user_id "system" to track actions that aren't tied into a specific user in a company.
It was never a technical problem, but a cognitive dissonance between the marketing and implementation details. I'll do my best to narrate my internal dialogue as a potential buyer.
I come to the homepage and am intrigued by the words "focused on companies"—because that is absolutely what I want! I want company level metrics (sports teams in my case) to be the first class citizen. I actually do not care about user identification at all. There are a ton of products that already do that I can pick if I want. I assumed you might be able to drill down into user level metrics eventually, but I thought our v1 would not identify users at all.
Jumping over to the docs, I head to the tracking behavior section for companies. The user_id param being required does not fit with my idea of what June is at this point. Why would I need to identify a user, if this analytics is focused on companies?
To me, this data model suggests that this is a traditional analytics product that treats user + user events as first class, then rolls that up to do clever things at the analysis level for companies. I had expected company events to be the first class citizen and for the events to flow top down from there. Now I'm concerned that when I stick in a 'team' user_id the data is going to be muddied, because the product won't know that this hacked in ID is just a generic company thing. Does that mean my user based analytics are going to be off? What does that imply for the data/reports downstream?
> There isn't really any drawback to that approach as you can filter out the system user from every analysis that doesn't want to include them! Happy to support you on the implementation or answer any further doubts in our Intercom conversation thread :)
This comment highlights what I mean. If you are an analytics company focused on tracking companies, I expected it to just work that way out of the box. If I need to remember to filter out this user from a bunch of metrics or analyses, I am bound to forget at some point or bring on a teammate who doesn't know.
Anyways, thanks again for the reply and hope the feedback is helpful.
I heavily considered June recently for my b2b saas (they even offered my tiny bootstrapped startup a small discount for the first year, which I appreciate very much).
The thing that stopped me was that there was no way to track an event to only a company, it still had to be tied to a user with the identify call. Our most important metrics ($ processed per company) is not based on a user at all. I wish June let you do company only event tracking - I would have had to hack in a fake user to track against.
Lots of our other metrics are per user, so we did like that it was possible to tie it to users-just surprising that an analytics company focused on org level analytics required it.
Also on the wishlist - hubspot integration. I’ve been evaluating Hightouch to punch data from my app to hubspot and it’s probably going to work, but take more effort than I was hoping for.
I think I’m in your target market-I own a small b2b saas that will be adding user generated automations to our product soon.
I love the UI and would use a UI only version of this. I pay for highcharts and pintura.
The backend stuff is not super helpful in my case because my app already has all those capabilities (email, SMS, etc) and it’s wrapped up in messaging within the app. I wouldn’t want to use an outside provider for that stuff. I also generally want custom automations - otherwise I would just be using Zapier - so while the example basic stuff is reasonable, I would be looking for a fully custom option for each building block.
I'm a target customer where I have a few curious customers, but I'm not fully ready to roll it out yet across the customer base. One thing that's stopping me, what does credits mean on your pricing page? And what is the pay as you go price after you hit your limit? I would need to be able to budget this before I deploy.
The second piece - we already have a CLI, which is great for terminal based agents and what we will continue to recommend. What we really want, and I think is what you are offering, is basically an easier way to deploy a 'remote connector' to use Claude lingo so that normal users with the claude/chatgpt app can just use our MCP. Can you point me to guidelines or the right place in your open source templates to understand how I would best handle auth (or the tradeoffs in each) during the initial build phase of the MCP server?