Hey everyone,
I’m working on a tool and wanted to gauge interest before going deeper.
The idea is a fully serverless service where you can:
• Bring in data from REST, GraphQL, gRPC, Databricks, Snowflake, MongoDB, MySQL, etc.
• Write (or vibe) lightweight JavaScript scripts
• Quickly build internal APIs or orchestrate existing APIs
No infra to manage, no services to deploy—just connect sources and ship.
Core use cases:
1. Building internal APIs on top of existing data sources
2. API orchestration (fan-out, stitching, transformations)
Current status:
• Pre-beta
• Focused on speed and minimal code
• Private beta access available in ~2 weeks
I’d love feedback on:
• Would you actually use something like this?
• What would be a deal-breaker?
• Who do you think this is most useful for?
Not selling—just validating whether this solves a real problem.
0 comments
—
Ask HN: Serverless Internal APIs and Orchestration · HackerTrans
The idea is a fully serverless service where you can: • Bring in data from REST, GraphQL, gRPC, Databricks, Snowflake, MongoDB, MySQL, etc. • Write (or vibe) lightweight JavaScript scripts • Quickly build internal APIs or orchestrate existing APIs
No infra to manage, no services to deploy—just connect sources and ship.
Core use cases: 1. Building internal APIs on top of existing data sources 2. API orchestration (fan-out, stitching, transformations)
Current status: • Pre-beta • Focused on speed and minimal code • Private beta access available in ~2 weeks
I’d love feedback on: • Would you actually use something like this? • What would be a deal-breaker? • Who do you think this is most useful for?
Not selling—just validating whether this solves a real problem.