I built a milestone-based B2B escrow system using Stripe Connect(Laravel+NextJS)

Show HN: React and NextJS lessons and exercises embedded in VSCode / Cursor

Simple NextJS deployment engine built with Go

I moved my website from NextJS to Phoenix

Hi all!I&#x27;ve built a small tool to visualize how inefficient `docker pull` is, in preparation for standing up a new Docker registry + transport. It&#x27;s bugged me for a while that updating one dependency with Docker drags along many other changes. It&#x27;s a huge problem with Docker+robotics. With dozens or hundreds of dependencies, there&#x27;s no &quot;right&quot; way to organize the layers that doesn&#x27;t end up invalidating a bunch of layers on a single dependency update - and this is ignoring things like compiled code, embedded ML weights, etc. Even worse, many robotics deployments are on terrible internet, either due to being out in the boonies or due to customer shenanagins. I&#x27;ve been up at 4AM before supporting a field tech who needs to pull 100MB of mostly unchanged Docker layers to 8 robots on a 1Mbps connnection. (and I don&#x27;t think that robotics is the only industry that runs into this, either - see the ollama example, that&#x27;s a painful pull)What if Docker were smarter and knew about the files were already on disk? How many copies of `python3.10` do I have floating around `&#x2F;var&#x2F;lib&#x2F;docker`. For that matter, how many copies of it does DockerHub have? A registry that could address and deduplicate at the file level rather than just the layer level is surely cheaper to run.This tool:- Given two docker images, one you have and one you are pulling, finds how much data docker pull would use, as well as how much data is _actually_ required to pull- Shows an estiimate for how much time you will save on various levels of cruddy internet- There&#x27;s a bunch of examples given of situations where more intelligent pulls would help, but the two image names are free text, feel free to write your own values there and try it out (one at a time though, there&#x27;s a work queue to analyze new image pairs)The one thing I wish it had but haven&#x27;t gotten around to fitting in the UI somehow is a visualization of the files that _didn&#x27;t_ change but are getting pulled anyhow.It was written entirely in Claude Code, which is a new experience for me. I don&#x27;t know nextjs at all, I don&#x27;t generally write frontends. I could have written the backend maybe a little slower than Claude, but the frontend would have taken me 4x as long and wouldn&#x27;t have been as pretty. It helped that I knew what I wanted on the backend, I think.The registry&#x2F;transport&#x2F;snapshotter(?) I&#x27;m building will allow both sharing files across docker layers on your local machine well as in the registry. There&#x27;s a bit of prior art with this, but only on the client side. The eStargz format allows splitting apart the metadata for a filesystem and the contents, while still remaining OCI compliant - but it does lazy pulls of the contents, and has no deduplication. I think it could easily compete with other image providers both on cost (due to using less storage and bandwidth...everywhere) as well as speed.If you&#x27;d be interested, please reach out.

Show HN: Docker pulls more than it needs to - and how we can fix it

I class myself as a product engineer and have worked with React, NextJS, PostgreSQL, PHP, Typescript etc.I am tired of using linkedin to find a new job.
I am looking for more smaller companies with remote work.Anyone know some sources to search?

Ask HN: Where to find cool companies to work for?

Hey HN,About 5 years ago, I built a weightlifting app for 5&#x2F;3&#x2F;1 that got me on the front page of HN [0]. After that, life happened. I had kids and so decided to get a job and put that project on ice. Eventually I grew too disappointed with my job, and decided to try building something again.The biggest feedback I kept getting from users was simple:
“Let me create my own programs.”That’s how Vis started.The initial idea was to create a B2B platform where gyms and trainers could build programs using formulas (e.g., percentages of 1RM) and reusable blocks instead of spreadsheets. I built what I still think is the best workout editor out there, but I quickly found out that B2B sales is hard (or maybe I just suck at it). It also just didn’t feel like a big enough sell for gyms.So I pivoted. I focused on the iOS app for a while [1], and now re-packaged the editor so individuals can use it directly.With Vis Pro, you can:- Define programs using formulas (e.g., 0.85 * SQUAT_1RM, or even better: RPE(8, SET_REPS) * SQUAT_1RM)- Build workouts by re-using pre-defined or even custom blocks- Share your programs and workouts with othersThe core idea is that programs are parametric instead of static. Change your 1RM and the entire program recalculates automatically.You can try it out without an account at <a href="https:&#x2F;&#x2F;vis.fitness&#x2F;pro&#x2F;try&#x2F;create-program" rel="nofollow">https:&#x2F;&#x2F;vis.fitness&#x2F;pro&#x2F;try&#x2F;create-program</a>The whole thing is built with NextJS, using Chevrotain (surprisingly solid) for the formula engine.It&#x27;s been super interesting using Codex since late Dec. It&#x27;s been a huge force multiplier, enabling me to ship really cool features like formula autocomplete and syntax highlighting in a couple of hours. I&#x27;m used to reviewing a lot of code from my time at Google, so that hasn&#x27;t been a problem, but it&#x27;s interesting to feel that the review speed is now the limiting factor. Though the codebase would become unmaintainable real quick without that.The next step is building an MCP server to allow users to create programs using LLMs and have them show up directly in the editor (and your phone).Would love feedback, whether you even lift or not![0] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31508009">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31508009</a>[1] <a href="https:&#x2F;&#x2F;apps.apple.com&#x2F;us&#x2F;app&#x2F;vis-next-generation-workouts&#x2F;id6743175121">https:&#x2F;&#x2F;apps.apple.com&#x2F;us&#x2F;app&#x2F;vis-next-generation-workouts&#x2F;i...</a>

Show HN: Vis Pro – A Formula-Based Workout Program Editor

okay, so this is not so big to many of you , but today , i was just bored and tired of doing any marketing , cos nothing seemed to have been working. so i decided to do a search (i searched for quite a number of keywords) like error tracking for supabase , error tracking for next Js , but my saas didnt rank (if you dont know what im building , im working on a dead simple error tracker that notifies you when something breaks in prod, no bloated dashboards or config hell) , i built this cos sentry had too much noise and i just wanted something that lets me know when there&#x27;s an issue in prod.so i decided to do a search on &quot;error tracking for shipfast(by marc lou)&quot; and guess what ?? Bugmail was the first recommended result , now i dont know how this worked, i mean ive done some seo and stuff but i wasnt expecting it , and now i feel like im back , which is funny cos i didnt make a sale , i didnt onboard a new user yet i feel like o have conquered , life of a founder , i guessi just wanted to share this here, also if you have any advice on how to rank higher on GSC and how to nail this marketing thing , any advice or feedback will be valuablein the meantime , incase you want to check out what ive built;you can check it out here ; https:&#x2F;&#x2F;www.bugmail.site

My small SaaS got recommended my Google in the AI search overview

I built Easemonitor to keep track of service uptime, response times, SEO, vulnerability scans, etc.
It&#x27;s 100 % open‑source (GPL‑3), runs in Docker on a cheap VPS and includes:NestJS API + worker with BullMQ queues
NextJS frontend with SSR caching &amp; image optimization
Prometheus metrics, Loki logs, Grafana dashboards, Jaeger tracing
JWT rotation, WAF rules, CSP&#x2F;HSTS, CVE audit scripts
Webhook DLQ, queue dashboard, healthchecks, maintenance mode
You can try it on my demo <a href="https:&#x2F;&#x2F;easemonitor.com" rel="nofollow">https:&#x2F;&#x2F;easemonitor.com</a>Would love feedback, contributions, or ideas for features.

Show HN: Easemonitor – self‑hosted uptime and performance monitoring

Hi HackerNews,Ruslan here.I once posted here a story how I got AWS $4k surprise bill for one day (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31907374">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31907374</a>), which is why I built DollarDeploy. I believe 95% of apps don&#x27;t need complicated AWS infrastructure and can be hosted using simple server from Hetzner, Digital Ocean, etc.Today I am launching an AI agent on DollarDeploy. The AI agent can automatically build and deploy your NextJS&#x2F;React, Go, Rust, or other types of apps to your own servers, running all commands via SSH on your server. You just type your commands or paste your GitHub repo link!DollarDeploy is similar to Dokploy expected there is no self-hosted version, because we want to offer a simple solution which you don&#x27;t configure and maintain - just add your GitHub repo and you are good to go.What makes DollarDeploy different is that we run apps as isolated Systemd processes on your server, and you can install Redis, Postgres, and other services to your host in a single click. Everything works locally, with low overhead as normal Linux processes, without the need of third party services.Try deploying your app — takes under 5 minutes. Looking for your feedback and opinion! Happy to answer any questions you have!FAQ: 1) To use DollarDeploy, you need to bring your own server or provision one directly through UI&#x2F;AI. 2) We have 14-day trial. 3) We are using OpenAI LLMs (probably will change soon) 4) You can use quick boilerplate to launch the app, or a template for open source software, including running GPT-OSS LLM model

Show HN: DollarDeploy AI, agent to deploy your web apps to production

After rebuilding my setup way too many times, I&#x27;ve finally landed on a stack that I don&#x27;t want to change. Took 6 years to get here, so figured I&#x27;d share what works for me.Here&#x27;s where it&#x27;s landed:Framework: Next.js 16 (App Router) React 19. Server Components, App Router for routing.Auth: Clerk Magic links, passkeys, MFA, social logins (Google, GitHub, Apple, etc.), user impersonation. It works perfectly with Next.js.Database: DrizzleORM Type-safe ORM. Works with PostgreSQL, SQLite, MySQL - but personally I prefer PostgreSQL. Drizzle Studio for exploring data, Drizzle Kit for migrations.Local dev: PGlite This one&#x27;s underrated. Full Postgres running locally, no Docker needed.Styling: Tailwind CSS Utility-first, fast iteration.Forms: React Hook Form + Zod Zod schemas validate on client AND server. Type-safe end-to-end.Testing: Vitest + Playwright Vitest in browser mode replaced React Testing Library for me. Playwright handles integration, E2E and visual regression. GitHub Actions runs everything on PRs automatically.Logging: LogTape Universal and unified logging for Browser, server and edge.Monitoring: Sentry + PostHog Sentry for errors (with Spotlight for local dev - game changer). PostHog for analytics and session replays.i18n: next-intl Built-in internationalization from day one. i18n-check catches missing translations before they hit prod.DX tooling:ESLint
Lefthook for git hooks
Commitlint + Conventional commits for consistent commits
Knip for catching dead code
Semantic Release for changelogs
Dependabot for dependencies update
Security: Arcjet Rate limiting and bot protection without thinking about it.I put this all together into a setup I reuse - nothing hidden, everything customizable. If anyone&#x27;s curious, the whole thing is documented here: https:&#x2F;&#x2F;github.com&#x2F;ixartz&#x2F;Next-js-BoilerplateWhat does your stack look like? Curious if anyone&#x27;s using different setups.

The tech stack I've been refining for 6 years

This was a fun project for an important use case - I hope this is valuable and can serve as a resource.Tech Stack: MapCN, NextJS, x API, AI SDK

Show HN: Situation Monitor

Hi HN,I am the developer behind I.T. Never Ends. It is a card-based resource management game (heavily inspired by Reigns) where you work IT support for a corporation taken over by eldritch horrors. You balance ticket resolution, budget, and entropy while dealing with printers that violate causality.I wanted to share a technical deep dive into how I built and packaged it, which I recently wrote about in a devlog: <a href="https:&#x2F;&#x2F;dadbodgames.itch.io&#x2F;it-never-ends&#x2F;devlog&#x2F;1388428&#x2F;building-a-system-for-the-absurd-why-it-never-ends-is-actually-a-website" rel="nofollow">https:&#x2F;&#x2F;dadbodgames.itch.io&#x2F;it-never-ends&#x2F;devlog&#x2F;1388428&#x2F;bui...</a>Here is a quick overview of the technical architecture and some lessons learned from the process:The Architecture:
The entire game is built in React and JavaScript. Under the hood, the game is essentially a giant state machine. While I have used engines like Godot for previous dynamic action titles, I am a full-stack developer by day (mostly NextJS). For a text-heavy, UI-driven game like this, I found the traditional object-oriented approach in standard engines required too much manual glue code to wire the game state to the UI. React&#x27;s declarative approach using state as truth allowed me to iterate incredibly quickly on the content itself, which makes up 90% of the gameplay.The Build Pipeline (Tauri vs. Electron):
Packaging a web application for Steam and the Steam Deck was the biggest hurdle. I ended up having to split my approach:Windows: I use Tauri. It is significantly lighter and creates a much smaller binary by hooking into the OS webview.Steam Deck &#x2F; Linux: I had to switch to Electron. SteamOS does not have a reliable pre-installed webview for Tauri to hook into out of the box. To handle robust save data persistence without relying on heavy Node.js filesystem modules, I wrote a small &quot;sidecar&quot; binary in Rust. The Electron frontend talks to this sidecar via JSON-RPC to handle atomic writes to the disk, which keeps the game running at a smooth 60fps on the Deck.The Data &amp; Community Pricing:
I have been fortunate to see over 10,000 plays on the Itch web build in the last two months, plus another 3,000 players on the Steam demo since February 1st.To gather player feedback efficiently at the edge, I built a custom system directly into the game client. The game has write-only access to a Supabase project. Players use an in-game, thematically fitting feedback form to submit friction points, purchase intent, and pricing data. This pipes directly into a Discord webhook via edge functions and is broadcasted live to our community. The idea is to let the community decide the final price of the game by popular vote (currently converging around the $12 to $13 mark).You can play the free web build on Itch here: <a href="https:&#x2F;&#x2F;dadbodgames.itch.io&#x2F;it-never-ends" rel="nofollow">https:&#x2F;&#x2F;dadbodgames.itch.io&#x2F;it-never-ends</a>
There is also a standalone Steam demo if you prefer: <a href="https:&#x2F;&#x2F;store.steampowered.com&#x2F;app&#x2F;4225400&#x2F;IT_Never_Ends&#x2F;" rel="nofollow">https:&#x2F;&#x2F;store.steampowered.com&#x2F;app&#x2F;4225400&#x2F;IT_Never_Ends&#x2F;</a>I would love to hear your thoughts and am happy to answer any questions about the React state management, the Rust sidecar, or the Steam Deck build pipeline!

Show HN: I built a card-based eldritch IT support game in React

Hi HN,I am the solo developer behind this.The Pitch:
It is a card-based resource management game (inspired by Reigns) where you work IT support for a corporation taken over by eldritch horrors. You have to balance ticket resolution, budget, and entropy while dealing with printers that violate causality.The Architecture:
The entire game is built in React&#x2F;JavaScript. Under the hood, it is basically a giant state machine. I chose this stack because it allowed me to iterate quickly on the UI and text-heavy elements, which are 90% of the gameplay. I&#x27;ve published other games that were more run of the mill and made in Godot, but I&#x27;m a full stack developer by day and most of my day-to-day is in nextJS. I just... I just missed easy state work, ok? Don&#x27;t shoot me. I was half afraid that building executables&#x2F;binaries for Steam would be a nightmare but it turned out (after a bit of futzing about with Tauri for linux) to be not too bad.The Build Pipeline (Tauri vs Electron):
Packaging a web app for Steam Deck was the biggest hurdle.Windows: I use Tauri. It is lighter and creates a much smaller binary since it uses the OS webview.Steam Deck &#x2F; Linux: I had to use Electron. SteamOS does not have a reliable pre-installed webview for Tauri to hook into out of the box.The Rig: I build everything using a Docker setup on a Windows machine to handle the Linux cross-compilation.The Data &amp; Feedback Loop:
The web build has seen 10,000+ plays on itch in the last 2 months with a 4.9&#x2F;5 rating.
An additional 3000 players have picked up the demo on Steam since February 1st.
To gather player feedback efficiently at the edge where the player is, I built a custom system directly into the demo:The game client has write-only access to a Supabase project.
An ingame (thematically fitting) feedback form allows the user to fill in purchase intent (0-10), pricing data, and friction points.This pipes directly into a Discord webhook via edge functions and it&#x27;s broadcasted live to the game&#x27;s discord server for everyone to see.
The idea is to let the community decide, by popular vote, what the actual price of the full game will be. Right now price seems to be converging around the 12-13$ price mark.The link above is to the free web build (Itch). I also just released a downloadable demo on Steam today if you prefer a standalone version: <a href="https:&#x2F;&#x2F;store.steampowered.com&#x2F;app&#x2F;4225400&#x2F;IT_Never_Ends&#x2F;" rel="nofollow">https:&#x2F;&#x2F;store.steampowered.com&#x2F;app&#x2F;4225400&#x2F;IT_Never_Ends&#x2F;</a>Happy to answer any questions about the React state management or the Steam Deck build issues.

Show HN: I.T. Never Ends – IT Support Simulator Built with React/Tauri/Supabase

Small open-source React component I made after getting tired of empty avatar placeholders in my apps &#x2F; SaaS.It generates a consistent avatar from a name and works well as a fallback when users don’t upload photos. No API calls.It comes with a NextJS helper to generate the same avatar as PNG and use them in your emails &#x2F; mobile apps.

Show HN: A tiny React lib for avatar fallbacks

Hi, I&#x27;m posting Daily Done, a web app for sharing project updates with clients - <a href="https:&#x2F;&#x2F;dailydone.work" rel="nofollow">https:&#x2F;&#x2F;dailydone.work</a>.Give it a try, it&#x27;s completely free right now.Concept - make it easy to share updates, and let clients see them without any friction (no signup required for clients). Clients can also react with emoji and comment.Goals - my day job is making web apps, but I&#x27;ve never shipped a product on my own. With this I wanted to create something that I could actually build, ship, and support end-to-end. So it is pretty simple (maybe too simple?).Tech stack
- NextJS... don&#x27;t hate me. Next has an annoying amount of magic, but I really like using it. Let&#x27;s me use React to generate plain HTML, and sprinkle in client-side JS for interactive bits.
- Sqlite &#x2F; Turso. Local dev without needing docker is really nice.
- WorkOS authkit, instead of rolling my own auth.
- Polar for billing, although billing isn&#x27;t currently active.Challenges
- The classic problem of getting people to try it out.
- Building something completely end-to-end was new for me. For example, setting up the webhooks and coordinating auth and billing isn&#x27;t hard, but took a bit of thought.
- I can&#x27;t design.Learnings
- Maybe don&#x27;t even build in billing, or possibly even auth, until people are trying it out.

Show HN: Share Project Updates with Clients

Hi HN!I created an ESP32 driven weather display for pilots that looks like a cockpit instrument. The goal was to move METAR off the phone screen and onto the desk where it is always visible. It’s a dedicated, &quot;always-on&quot; desk accessory that fetches real-time aviation weather and renders it onto a high-contrast e-paper display. It also has a quiz mode to help student pilots learn and test METAR decoding.Jumpseaters: Adding Personality to the Data
Raw METARs can be dry, so I implemented a feature called Jumpseaters. These are selectable personality profiles that transform the device into an opinionated flight crew.Instead of just seeing &quot;OVC001,&quot; you might get a report from Downwind Donnie, who sarcastically judges your &quot;personal minimums,&quot; or Checkride Charlie, a virtual DPE who delivers weather updates with the uncomfortable silence. It was a fun to map these &quot;personalities&quot; to specific weather triggers in the firmware.----The Technical DetailsController: ESP32-S3. I chose this for the native USB support and the power efficiency needed for long-term deep sleep.Display: 4.2&quot; E-Paper. It uses an open-source library <a href="https:&#x2F;&#x2F;github.com&#x2F;martinberlin&#x2F;CalEPD" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;martinberlin&#x2F;CalEPD</a>Power: Deep sleep cycles keep the current draw low, allowing it to run for weeks on a small LiPo. I am continuing to optimize the power usage because I feel I can get it to last many months even after the daily screen refreshes.Tech Stack: ESP-IDF&#x2F;C++ for the microcontroller. Flutter&#x2F;Dart for the iOS&#x2F;Android mobile apps. Nextjs for the website and API.---I have learned a lot about hardware devices during this process. It has been fun programming for the E-paper display. It has it&#x27;s own unique challenges because of the nature of the technology (seconds for each refresh vs. refreshes&#x2F;second for traditional screens). I really enjoy when it refreshes.The Kickstarter is live and 38% funded with 15-days to go. One thing I wish I had done a lot more of is prelaunch marketing. Ads now have had good conversion driving to the Kickstarter page, but the volume takes time.On the same prelaunch theme, the other major lesson learned is that I wish I had asked for more feedback publicly (I do have early testers, but all local) and shared more before working on the Kickstarter. Once you say Kickstarter, all the mods put it in the commercial category and don&#x27;t allow posting ANYTHING related to it.Check it out at <a href="https:&#x2F;&#x2F;papermetar.com" rel="nofollow">https:&#x2F;&#x2F;papermetar.com</a> or <a href="https:&#x2F;&#x2F;www.kickstarter.com&#x2F;projects&#x2F;charlie29r&#x2F;papermetar" rel="nofollow">https:&#x2F;&#x2F;www.kickstarter.com&#x2F;projects&#x2F;charlie29r&#x2F;papermetar</a>

Show HN: PaperMETAR – An E-Paper Aviation Weather Display for Pilots

Say hello to <a href="https:&#x2F;&#x2F;pongo.sh&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pongo.sh&#x2F;</a>self-hosted uptime monitoring, configured entirely in TypeScript and built on NextJS and Bun.No UI forms. No vendor lock-in. Just code in your repo.Monitors, dashboards, alerts, incidents, and status pages — all defined as TypeScript files and Markdown, version-controlled alongside your application.You can one-click deploy it to Vercel or anywhere you can run node&#x2F;bun&#x2F;docker.Your monitoring config lives in your repo like everything else.Want to know what&#x27;s monitored and why? Read the code.Need to review a change? It&#x27;s in the PR. Need to roll back a bad alert? Git revert.No more clicking through dashboards wondering who changed what and when.Built with Next.js, Drizzle ORM, and Bun. Runs with SQLite for simplicity or PostgreSQL for production.Fully open source and ready to use today.Would love to hear what you think and what features you&#x27;d want to see next, leave a star on GitHub<a href="https:&#x2F;&#x2F;github.com&#x2F;TimMikeladze&#x2F;pongo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;TimMikeladze&#x2F;pongo</a>

Show HN: Pongo – a self hosted uptime monitor using configuration as code

Montage is a fork of Remotion&#x27;s NextJS template, set up for coding agents to quickly produce motion graphics videos.In May 2025 I commissioned a team of motion designers to create a launch video. It cost us $2000 and 4-5 days of my full attention.I noticed the video was likely built using a set of animations and transitions that this motion design team reused for all their customers. My theory was that if I could recreate that set of animation primitives and put them in a format coding agents could understand, I&#x27;d be able to create launch videos end-to-end way faster and have full control over the final product.I spent 3 days setting up the repo and 4 hours building the motion video you see above. Those 3 days consisted of 1) building out the set of primitives and 2) building the iterative agent rendering loop so the agent could work autonomously.The primitives I built were:Text (word drag-in, flip-up, gradient fill, typing animation)
Motion (object pop in, fade right, fade left, swoop, float, etc.)
React components (logo, cursor, animated browser, animated terminal)
Background designs (radial gradient, corner gradient, color fade, etc.)The way I built these primitives was surprisingly simple. I leveraged Gemini&#x27;s ability to analyze videos (Claude and GPT don&#x27;t accept videos as a modality yet) by attaching the previous motion-designed video and giving it this prompt:&quot;Is it possible for you to thoroughly go throughout the video and, in detail, note all the different text transitions and what they look like, describing them in natural language so I can put them in my animation tool?&quot;It gave me a text file which I dumped into a coding agent (in my case Claude Code) to build animation primitives with. I repeated that for motion transitions and background designs, and modified existing React components to work with Remotion.For building the iterative agent rendering loop, I gave the agent the ability to test its sections end to end.Remotion can render individual frames via a bash command (npx remotion still {flags}) so I put in the AGENTS.md to heavily use that when designing sections. I also tried having the agent browser-use the Remotion editor spun up as a local dev server, but this was too confusing — it had to know how to scrub through frames in the UI, select the right sequence to check, etc. So I ended up sticking with the Bash command and found that coding agents could do a decent job testing animations by rendering frames 10-20 steps apart.I&#x27;d love for you to try this out and welcome any feedback. Montage has really helped me create high-quality motion videos (an example is in the repo).

Show HN: Montage – Quickly build product launch videos with coding agents

I built ReportBurster out of frustration with current BI stacks.Most tools live in two separate worlds:- Beautiful dashboards and analytics tools — great for charts, weak for reporting, and many push you towards their SaaS. 
- Powerful report generators — pixel-perfect PDFs, but no real analytics or exploration.Stitching 4–5 tools together with scripts, glue code, and workarounds became the norm.Plus, most modern tools are SaaS-first. If you want serious reporting, automation, portals, or embedding — self-hosted and open-source — options shrink fast.ReportBurster aims to handle the entire data-to-delivery pipeline in one platform, powered by the *AI Crew* — your council of AI oracles that learn your projects, preferences, and workflows:- Explore &amp; visualize data (aka Chat2DB using AI) 
- Generate pixel-perfect reports 
- Automate bursting and distribution 
- Build secure document portals 
- Build, deploy, or embed dashboards and OLAP analytics directly into your own appsBuilt with Angular, Java, and NextJS. Fully self-hosted and open-source — *no more SaaS lock-in*.GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;yourusername&#x2F;reportburster" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yourusername&#x2F;reportburster</a> 
Website: <a href="https:&#x2F;&#x2F;www.reportburster.com" rel="nofollow">https:&#x2F;&#x2F;www.reportburster.com</a>I’d love feedback on usability, feature ideas, or contributions!

Show HN: ReportBurster – Self-hosted all-in-one tool for analytics and reporting

# This is a NextJS
NextJS is a **framework for ReactJS**.

Wait a second ... a "framework" for React? Isn't React itself already a framework for JavaScript?

Well ... first of all, React is a "library" for JavaScript. That seems to be important for some people.

Not for me, but still, there is a valid point: React already is a framework / library for JavaScript. So it's already an extra layer on top of JS.

## Getting Started

Create Next App:

```bash
npx create-next-app
# or
yarn create next-app
```

First, run the development server:

```bash
npm run dev
# or
yarn dev
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.

You can start editing the page by modifying `pages/index.js`. The page auto-updates as you edit the file.

[API routes](https://nextjs.org/docs/api-routes/introduction) can be accessed on [http://localhost:3000/api/hello](http://localhost:3000/api/hello). This endpoint can be edited in `pages/api/hello.js`.

The `pages/api` directory is mapped to `/api/*`. Files in this directory are treated as [API routes](https://nextjs.org/docs/api-routes/introduction) instead of React pages.

## Why would we then need NextJS?

Because NextJS makes building React apps easier - especially React apps that should have server-side rendering (though it does way more than just take care of that).

In this article, we'll dive into the core concepts and features NextJS has to offer:

- File-based Routing
- Built-in Page Pre-rendering
- Rich Data Fetching Capabilities
- Image Optimization
- Much More

## File-based Routing

![Create routes via your file + folder structure](nextjs-file-based-routing.png)

# File-based Routing In Action

![Create routes via your file + folder structure](nextjs-file-based-routing-in-action.png)

## Learn More

To learn more about Next.js, take a look at the following resources:

- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.

You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!

## Deploy on Vercel

The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.

... More content comming soon ...

NextJs News

News From: hn.algolia.com