A Redshift-native SQL IDE for VS Code, with an MCP server built in.
Two channels, because the answers come from different places.
Bugs, features and questions about the free RedLens extension go to its issue tracker:
github.com/redlens-io/redlens/issues
It is a public repository under MIT, so pull requests are welcome the same as in any open project. If you think a paid feature belongs on the free side, open an issue and make the argument — the tier map is public precisely so that conversation can happen.
Never paste credentials, endpoints or real query results into a public issue. Redact anything that identifies your warehouse; a schema shape is almost always enough to reproduce a problem.
If you bought a licence, write to support@lensql.dev or reach us through the Polar customer portal linked from your purchase confirmation email. The portal is tied to your licence, so we can see what you bought without you having to prove it; email works when you would rather just write.
Reasonable-effort response, usually within two business days. This is a one-person project and that is stated plainly rather than dressed up as a guarantee.
Enterprise support with a response-time SLA is available on request — along with invoicing, purchase orders, and help with air-gapped or private-marketplace distribution. Ask through the same portal, or open a discussion if you are evaluating and have not bought yet.
Formal notices under the EULA (section 20.5) go to support@lensql.dev with the subject marked “Legal notice”.
Purchases are handled by Polar, our merchant of record. Invoices, receipts, payment method changes and cancellations are in their customer portal, linked from your purchase confirmation email.
Refunds within 14 days, no questions asked — write to us or use the portal.
Please do not open a public issue for a security vulnerability. Use the private advisory form:
See SECURITY.md for what is in scope and what to expect.