Technical fit
Review identity, permissions and tenant-aware data access against your planned architecture. Bring questions about your stack, application boundaries and the capabilities your client needs.
For software agencies
A reusable .NET SaaS foundation for software agencies planning and building new client products.
Features · workflows · customer experience
Identity · access · customer data boundaries
Integration · testing · handover
Architecture alignment
Reusable capabilities
Responsibilities and access
Discuss by enquiry
Start with the client project
Your client’s product has its own requirements, business rules and user experience. Start your evaluation with those needs.
Assess which Minelics foundations fit the proposed application, where your team would extend them, and what the integration work involves. Use that understanding to inform your architecture and delivery plan.
Architecture workshop
Business requirements · user experience
Reusable structural capabilities
Architecture · integrations · testing
Review the project, not just the platform
Technical fit, delivery fit and client handover are distinct decisions.
Review identity, permissions and tenant-aware data access against your planned architecture. Bring questions about your stack, application boundaries and the capabilities your client needs.
Walk through the developer tools and starter examples. Identify what your team could reuse and what it would need to implement, adapt and test for the client’s product.
Discuss the questions that matter beyond the initial build: licensing, access to relevant code and documentation, maintenance responsibilities and the client’s intended use.
See the foundation in context
A guided demo connects the product discussion to your next SaaS project. Explore the Developer Hub and selected setup workflows with Minelics’s founder, and discuss the foundation capabilities relevant to your build.
Developer Experience · Concept
A clear starting point for your SaaS foundation
B2B2BModel selected at initialization
Illustrative UX · release capabilities to be validated
Module catalogue · Concept
Explore capability boundaries before adopting a module.
Illustrative capability boundary. Review availability, integration requirements and evidence in a guided assessment.
Illustrative capability boundary. Review availability, integration requirements and evidence in a guided assessment.
Illustrative capability boundary. Review availability, integration requirements and evidence in a guided assessment.
Illustrative capability boundary. Review availability, integration requirements and evidence in a guided assessment.
Editable UX concept. Module availability and operational behaviour must be validated against the actual product.
API Explorer
Inspect example requests and responses. No live API calls.
/api/v1/tenantsPreview only →Request / example
{
"filter": "active",
"page": 1,
"pageSize": 10
}Response / example EXAMPLE
{
"data": [
{ "id": "example-123",
"status": "active" }
]
}Illustrative API concept and sample data. Endpoint contracts and behaviours require product validation.
Minelics is in active development. We’ll confirm the available capabilities and evaluation scope for your project.
Commercial arrangements
Commercial pricing is available by enquiry.
Tell us how you intend to use Minelics and what the client will need at handover. Questions about multiple client projects, redistribution, maintenance and ongoing support can then be addressed in the commercial discussion.
New SaaS products being planned or built with .NET. Our initial audience is software agencies in Australia and New Zealand.
A short description of the proposed product, your intended stack and the questions you need answered. Existing architecture decisions or client handover requirements can help focus the discussion.
For your next client build
Review the foundation, ask technical questions and discuss commercial use.