IXYS builds and operates pragmatic software for information systems: web apps, APIs, automation, and infrastructure tooling. Our focus is simple: ship reliable things that stay reliable.
- Products & services: web apps, APIs, back-offices, workers
- Tools & components: packages, libraries, SDKs, templates
- Infrastructure & operations: CI/CD, manifests, IaC, observability, runbooks
- Documentation: conventions, ADRs, operations guides
- Simplicity (the kind that survives 3 years in production)
- Traceability (logs, metrics, written decisions)
- Automation (repeating yourself is cheating)
- Security (secrets stay secret)
Depending on the repository, contributions may be open-source or internal-only. When it’s open:
- Check the repo README (scope, setup, and expectations).
- Open an issue for bugs / proposals (if issues are enabled).
- Submit a PR with:
- Clear context and rationale
- A test plan (how to verify)
- Tests when it matters (and it usually matters)
General rules:
- One PR = one topic.
- No secrets in commits (ever).
- Prefer small, reviewable changes over “big bang” PRs.
Security issues:
- Do not open public issues for vulnerabilities.
- Follow the repo’s SECURITY.md (or the org policy if defined).
- Repository-level docs live in each repo’s
README.mdand/docsfolder when present. - Operational notes may live in
runbooks/orops/directories (repo-dependent). - Architecture decisions may be tracked as ADRs (commonly in
docs/adr/).
If you don’t find what you need:
- Open a documentation issue (when enabled) with the page/section you expected to exist.
We'll tell you that later 😉