Steelax
Contact

Tell us what you are building and what keeps stalling.

Every request is read by someone who works on the product. Tell us enough about your stack and the problem in front of you and we will come to the first conversation already useful.

Request access

Fields marked with an asterisk are required. The rest help us prepare, and you can skip them.

If you are sending a security questionnaire or a procurement form, say so here and we will reply with the current documentation.

Submitting opens your email client with the message ready to send.

Your message is ready. Your email client should be opening with everything filled in. If nothing happens, write to us directly at the address in the panel beside this form.

What happens next

  1. We reply within one business day

    A real reply from someone on the product team, with a view on whether Steelax fits what you described.

  2. A working session, not a demo

    Forty-five minutes with your tracker and one repository connected, looking at a problem your team actually has.

  3. You decide what happens after

    Anything created in the session stays in your systems whether you go further or not.

Reach us directly

General and access requests
hello@steelax.net
Security and disclosure
security@steelax.netAcknowledged within one business day
Billing and accounts
billing@steelax.net
By phone
(951) 345-5629Weekdays, 9am to 6pm Pacific
Postal address
Steelax, LLC
5111 Avenida Oriente
Tarzana, CA 91356
United States

Before you write

It helps to know which issue tracker you use, roughly how many repositories are in play, and one specific thing that went wrong recently. That is usually enough for us to be useful in the first reply.

Questions

Before the first conversation.

Do we need to connect anything before we talk?

No. The first conversation is about your product and where the handoff hurts. If you want the session to be hands-on, connecting one tracker and one repository beforehand with read-only scopes makes it far more useful, and we will help you do it.

Will we be passed to a salesperson?

No. We are small enough that the person who answers your message is someone who works on the product, and that stays true through evaluation and after you are a customer.

Can you answer a security questionnaire first?

Yes. Say so in your message and we will send the current documentation set, including our questionnaire responses and the most recent penetration test summary, under a mutual non-disclosure agreement. Most of what reviewers ask is already answered on the security page.

We are not ready to buy. Is it still worth getting in touch?

Yes, and plenty of the teams we work with took months. Tell us where you are and we will be straight about whether now is the right time. We would rather have a useful conversation this quarter than a wasted one this week.